Troubleshoot missing Autopilot updates

Start with the repository link and Activity. A missing suggestion can mean no event arrived, the event was filtered, no documentation update was needed, or processing failed.

Check the connection

Confirm the link is enabled, its repository and branch match the change, and provider authorization is still active. For GitHub App connections, check the app remains installed for the repository. Complete any manual provider webhook setup required by the connection.

Check the event

Look in Activity for the relevant time. If no event exists, inspect provider delivery and trigger configuration. If an event was ignored or produced no suggestions, compare changed paths with the filters and consider whether the code change affects the documented behavior.

Documentation-only, dependency-lockfile and very small changes may be skipped. Repeatedly pushing an irrelevant change is not a useful way to test documentation coverage.

Check access and credits

Preview and apply permissions differ. An upgrade prompt on Apply does not mean the suggestion failed to generate. If processing is paused or fails, inspect the visible reason and account usage.

Check the documentation scope

A Space needs relevant content to maintain. If the major problem is missing topics across the project, use Update Documentation Gaps for a deliberate expansion.

When contacting support, include the Space, provider, repository, branch, approximate event time and visible status. Keep secrets out of screenshots. If a change may already have applied, inspect the target page before trying the action again.