Review activity and audit history

Use a Space's Autopilot Activity view to understand repository processing and documentation changes. Activity is the first place to investigate an expected update that did not appear.

Read the event outcome

Look for the relevant repository and time. Events may be processing, completed, ignored or failed. A completed event can legitimately produce no suggestions when the changed code does not require a relevant documentation update.

For generated batches, inspect the suggestions and their applied or discarded outcomes. Distinguish an event being received from a page actually being changed.

Configuration history

Where your plan includes audit logging, inspect link creation, updates, enable/disable actions and related maintenance changes. Entries identify the action, actor and affected object with a timestamp.

Use the available CSV export when you need an offline review. Store the export appropriately: actor information and other operational details may be included.

Investigate a problem

Collect the Space, repository, branch, approximate time and the relevant event or batch identifier. Compare configuration changes around that time with the observed outcome.

If content was applied incorrectly, inspect the updated page and available version history. Avoid deleting the Space or event context before requesting support.

For programmatic review, supported assistants can retrieve Space activity through MCP capabilities, subject to normal permissions and entitlement.