> For the complete documentation index, see [llms.txt](https://sandgarden.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sandgarden.gitbook.io/docs/meta/troubleshooting-and-faq.md).

# Troubleshooting and FAQ

Symptom-first answers to the problems that actually come up.

Symptom-first answers to the problems that actually come up. Each section: what's happening, how to fix it, and how to avoid it next time.

### I mentioned @doc.holiday and nothing happened

The mention must come at the **start** of the comment: `@doc.holiday, update the install guide` works; a mention buried mid-paragraph doesn't. If the mention was first and there's still no 👀 reaction, check three things in order:

1. The repository is connected as a Source and its connection is **Healthy** ([manage connections](/docs/sources/manage-connections.md)).
2. A [Publication](/docs/publications/publications.md) includes that repository among its Sources.
3. You have write access to that Publication.

If all three hold and there's still no entry in [Work History](/docs/working-with-doc-holiday/work-history.md), the request never reached Doc Holiday; re-check the connection's health and try once more.

### My Source shows Unhealthy

Doc Holiday automatically retries temporary GitHub authorization and access failures. The Source can recover before it enters a persistent **Unhealthy** state, without a configuration change.

If the Source remains **Unhealthy**, permanent credential, provider installation, repository, or access problems require repair. Doc Holiday stops reading the Source until the problem is fixed, so its information can go stale while existing docs remain unaffected.

Open the Source in [Manage Connections](/docs/sources/manage-connections.md), update the credentials or reinstall the provider application, and confirm the badge returns to **Healthy**. Details per provider: [Connect GitHub](/docs/getting-started/connect-github.md), [GitLab](/docs/getting-started/connect-gitlab.md), [Bitbucket](/docs/getting-started/connect-bitbucket.md).

### One GitHub file cannot be read

If Doc Holiday cannot read one GitHub file, it continues processing the other readable files in the repository. The unreadable file does not stop processing for the rest of the repository.

### An entry says Needs Attention

**Needs Attention** means Doc Holiday is asking *you* something. Open the entry's **Messages** tab, read the question, and reply. Your reply starts a new pass and the work continues.

### The draft touched files I didn't want

Two remedies, in order of immediacy:

* **Now:** in the entry's **Files** tab, exclude the files you don't want before approving; excluded files stay out of the pull request.
* **Next time:** scope the request in both directions ("update X; don't change Y"). See [Writing requests](/docs/prompting-guide/writing-requests.md).

### A request errored

Open the entry and retry the failed pass. If it fails again on a Bring Your Own Key or Open Source Software plan, check [AI provider keys](/docs/administration/ai-provider-keys.md): a rejected or removed key stops all writing work, and on the Bring Your Own Key plan a lapsed subscription does the same ([Billing and plans](/docs/administration/billing-and-plans.md)).

### The docs pull request has merge conflicts

Doc Holiday's PRs are ordinary git PRs, and they age like anyone else's. If the docs repo moved on and the PR conflicts, close it and send the request again. A fresh run drafts against the current state of the repo, which is usually faster than resolving conflicts by hand.

### It wrote about the wrong thing

The request was probably broader than it felt when you typed it. The fix is steering: name the outcome, pin the file path, and set boundaries. The [Prompting guide](/docs/prompting-guide/prompting-guide.md) is the five-minute version, and durable preferences belong in [style guides](/docs/prompting-guide/writing-style-guides.md) rather than repeated in every request.

### It keeps making the same stylistic mistake

Add the rule that would have prevented it to your style-guide instruction: one checkable rule per recurring miss ([Writing style guides](/docs/prompting-guide/writing-style-guides.md)). Corrections sent as requests fix one page; rules fix every future page.

### FAQ

**Who can see my code?** Doc Holiday reads the Sources you connect and stores what it needs to write well; drafts stay in Doc Holiday until you approve them. The full story: [Security and data handling](/docs/administration/security-and-data-handling.md).

**Can I run it on a schedule?** There's no built-in scheduler; use [triggers](/docs/publications/configure-triggers.md) to react to merges and releases, or the [GitHub Action](/docs/automation-and-integrations/github-action.md) from a scheduled CI workflow.

**Which git providers are supported?** GitHub, GitLab, and Bitbucket; see [Getting started](/docs/getting-started/quickstart.md).

**Does someone have to review every change?** Yes, by design. Work stages for review and becomes a pull request only when a person approves it ([Review and revise](/docs/working-with-doc-holiday/review-and-revise.md)).

***

<p align="center"></p>

<p align="center">Docs authored by <a href="https://doc.holiday">Doc Holiday</a></p>