Checking a repository's sync status

Amendary checks every connected repository once a day, comparing what changed in your code against the documentation pages you've mapped to it. This article explains how to read a repository's status so you know when it was last checked, whether that check succeeded, and how to trigger a check immediately instead of waiting for the next scheduled run.

What you can see for each repository

For every repository connected to your workspace, the dashboard shows:

Last checked at: the date and time the daily check last finished for this repository. If this is empty, the repository has never been checked.
Last check result: whether the run completed cleanly, failed, or completed only partially.
Pending corrections: the number of suggested corrections still waiting for review across the pages mapped to this repository.

<aside> ✏ A repository that shows no last-checked time isn't broken. It simply hasn't been through a daily check yet, for example because it was just connected.

</aside>

Reading the check result

The result reflects the outcome of the most recent check, not a running average:

Result	What it means
Succeeded	The check completed and every mapped page was compared against what changed.
Partial	The check completed, but part of the change history was too large to process in one pass. Corrections from a partial check are still delivered, but they're marked as based on incomplete evidence.
Failed	The check could not complete. Your documentation was not compared against the latest changes, so any corrections you see are from an earlier check.

<aside> ⚠ While a repository shows a failed result, the corrections in your review queue may be based on an older version of your code. Trigger a new check once the underlying issue is resolved, rather than relying on the last successful result.

</aside>

A failed check most often points to a connection problem, for example a GitHub or Notion connection that has lost access. Check your connected accounts to confirm they're still authorized, since a check can't read a page or a repository it no longer has permission to reach.

Triggering a check immediately

You don't have to wait for the daily run to see whether recent changes have made a page stale. Any member of your workspace can trigger a check for a repository on demand.

Open the repository's entry in your dashboard.
Select Check now.

Result: the repository's status updates to reflect that a check is in progress. When it finishes, Last checked at updates to the current time and Last check result reflects the outcome. Any new corrections appear in your review queue if your workspace is set to manual review, or are applied directly to the affected page if it's set to apply confident corrections automatically.

<aside> ✏ Only one check can run for a repository at a time. If a check is already running, whether it started from Check now or from the daily schedule, a new request waits rather than running alongside it.

</aside>