Troubleshooting

Check that it was included when you installed the GitHub App. To adjust which repos it can see, use “Manage repos on GitHub” next to the account on the Repos tab; changes there sync back automatically. Also check you have not hit your plan’s repo limit on Settings > Plan & billing (limits are on the pricing page).

That account or organisation already had Amendary installed, so GitHub showed its settings page instead of returning to Amendary. Select “Connect GitHub” on the Repos tab again: it lists the accounts and organisations where Amendary is installed, so you can pick that one.

Amendary can only see pages you shared with the integration when you connected Notion, and Notion search is not exhaustive. If a page is missing from Browse on the Notion card, reconnect Notion and select it (or its parent) in Notion’s picker. Or open the … menu on the Notion card, select Add a page by link… and paste its link. Pages inside a database appear when you expand that database in Browse.

The page was deleted or unshared in Notion, so Amendary can no longer read it and stops checking it. It is hidden from your watched list; you can show gone pages to review them. If it still exists, reconnect Notion and select it again; if it is really gone, you can remove it.

The article was deleted in Zendesk or Intercom, so Amendary stops checking it. Unwatch it, or restore it in the help center and select Browse again.

On the Pages tab, confirm an owner enabled a GitHub docs destination for that repo and chose the correct folder or wiki. Select Refresh on its card to scan for Markdown files added since the last scan, then open Browse to watch the file. A discovered file is not checked until you watch it.

Zendesk or Intercom refused the sign-in Amendary holds. Reconnect as above. If it keeps happening, disconnect the connection and add it again with Add destination.

Amendary asks for your Zendesk subdomain only. For acme.zendesk.com, enter acme.

There is no Browse button until an owner sets Help articles follow on the card: a repo or a changelog URL. Then Browse lists the articles. See Help articles follow.

Amendary lists published Intercom articles only. A draft is not listed. Publish it in Intercom, then open Browse again. Zendesk is different: it lists drafts too, marked Draft.

Intercom needs more than one language turned on in its help center before it accepts a translation. Turn on the language in Intercom’s help center settings, then try again.

The help center asked Amendary to slow down. Nothing was changed. Wait a minute and try again.

A help center that follows a repo uses the repo’s What counts as shipped, and nothing may have shipped that way yet. The usual case: GitHub Releases is chosen but the repo has never published one, so there is nothing to check against. Open the Repos tab and look for the “Nothing has shipped this way yet” warning. Then either publish a release or push a tag, set the branch name, or switch to commits, which needs no setup. A help center that follows a changelog URL is checked only when a new dated entry appears; the destination’s card on the Pages tab shows when it was last read and what was skipped.

On the Pages tab, look at the page’s audience. If it shows “Checks paused”, set an audience again to resume checks. Then look at the role of each repo on the page: a Background only repo starts no check unless Check when this repo changes too is ticked. Set the repo the page is about to Describes this repo.

Your team reached today’s usage limit. It is a safety cap set by Amendary, and checks resume at the next midnight in your team’s timezone (Settings > General). Settings > Usage shows your usage and the days checks were paused. If you hit it often, email us at hello@amendary.com.

Nothing on GitHub, Notion, Zendesk or Intercom was changed. But Amendary deleted what it held for that connection: its corrections, check results and product-update entries. Reconnecting does not bring them back. Reconnect from the Repos tab, the Pages tab or Settings > Integrations, then check that your pages are still watched and mapped. A reconnected repo is checked from its latest commit on.

Open Generate docs, then History, and select the run to see its status and continue it. Check the credit estimate against your balance before starting. A restart on our side does not stop a run: it resumes on its own. If a run stops before producing drafts, its held credits are refunded; a run with drafts can be reviewed and resumed. Activity shows the reason a run stopped. See Billing & plans for how generation credits work.