Troubleshooting

Find your symptom below. Each answer says what is happening and what to do.

The first run failed#

Open the project and read the message on the run.

• "This repository has no readable text files." Every file was skipped by the filter or by your ignore paths. Check AI guidance and the repository contents.
• "GitHub could not find owner/repo@branch." The repository or default branch is not reachable. If it is private, make sure the Docup GitHub App can access it.
• "We could not start writing your docs." Docup could not reach its background workers. Choose Try again.
• "No page could be written." Every page failed. Choose Try again. If it keeps happening, reduce what Docup reads with ignore paths.

Retrying a first run counts toward your 10 runs per day.

One page failed#

Open the page and choose Retry, or write it yourself. See Runs.

A page is short or thin#

The Overview flags pages under 150 words. Open them and add detail, or add instructions in AI guidance so future pages go deeper.

My site shows "not found"#

• Is the site published? Drafts are not public. Choose Publish docs.
• Did you unpublish the site, or the last live page? Publish again.
• Did you change the address? Links to the old address stop working. See Site and domain.

My docs did not update after a push#

Check these in order:

1. Is the project connected through the GitHub App? Projects made from a public link never update. See Connecting GitHub.
2. Was the push to the default branch? Other branches are ignored.
3. Did a documented file change? If no page was written from the changed files and nothing new needs documenting, the update finishes with "No docs changes needed".
4. Look at Runs. Every update appears there. A failed update shows why.
5. Did you hit the daily limit? A workspace can run 15 AI updates per day. The next push after midnight UTC catches up.
6. Did you edit the page? Edited pages get a suggestion instead of new text. Open the page and look for the update banner. See Keeping docs up to date.

An update changed my live site#

That is expected for pages you have not edited, on a site that is already live. If you want to review every change first, edit the page once, and later changes will arrive as suggestions.

Ask AI is missing or not answering#

• Ask AI needs a published, public site with Ask AI turned on in the Ask AI section.
• It answers only from published pages. Check the group each page is in.
• "I could not find anything about that in the docs. Try asking in other words, or about something the docs cover." No documented sections matched the question. Ask again in other words, or add the topic to a page.
• "You have used your 15 questions for today. Come back tomorrow." You reached your daily visitor limit of 15 questions.
• "You are asking too fast. Wait a minute and try again." You hit the per-minute limit. Wait a minute before asking again.
• "We could not check that you are a person. Reload the page and try again." The Turnstile bot check failed. Reload the page.
• "Ask AI has answered all the questions it can for today. Try again tomorrow." Either the site-wide daily limit of 500 questions or the system-wide daily limit of 5,000 questions has been reached.
• "Ask AI is not available right now. Try again in a moment." or "Ask AI could not answer. Try again in a moment." The rate limiting database or model connection is temporarily unavailable. Wait a moment and try again.

My site is not in Google#

• Search engines must be on in Search and sharing.
• Pages hidden from search with the page option are left out of the sitemap.
• New sites take time to be crawled. Submit /sitemap.xml in Google Search Console to speed it up.

Changes I saved are not visible to readers#

Edits are drafts. Use Preview to see them and Publish changes to send them live.

Analytics show no visits#

Analytics count visits to the published site, not to Preview. A new site shows a notice until its first visit arrives, and results are cached for five minutes.