Autopilot activity log

Every Autopilot run is logged. Use the activity log to audit what changed, when, and why.

Where to find it

/autopilot → scroll to the Activity Log section near the bottom of the page (it's not a separate tab).

What's in each entry

The list renders one row per logged event:

Element	Meaning
Timestamp	Relative time ("3 hours ago") for run start.
Status badge	`success` (green), `failed` (red), `skipped` (blue), `neutral` (other).
Rule type badge	Which capability fired — `meta_descriptions`, `image_compression`, etc.
Summary text	Human-readable run summary, e.g. "Compressed image on 'Hydrogen' — 2.4MB → 0.6MB (75% saved, replaced original)".
Items count	How many resources were touched in this run.
Duration	Total wall-clock seconds.

Filters

Two <s-select> filters at the top of the section:

Filter by rule type — narrows to one capability (e.g. just image_compression).
Filter by status — narrows to success, failed, or skipped.

There's also a Refresh button to re-fetch and an Export button that downloads the filtered list as CSV.

Why "Fixes this month" differs from the Dashboard

Dashboard's "Fixes this month (all)" includes manual + one-click + autopilot fixes. The Autopilot activity log scopes to autopilot-driven fixes only — that's why the numbers differ. Both are correct for their scope (per CLAUDE.md Known Issue #4).

Debugging a run

If a run shows "items processed: 0" repeatedly:

Check rule scope. Make sure the rule is enabled and your store has resources matching it. (No tag-filter UI yet — it's all-or-nothing per rule.)
Check wallet balance. Wallet-low aborts AI-driven rules with a clear summary; non-AI rules continue.
Check Shopify API health. Search-data delays don't stop Autopilot; only Shopify mutation 5xx errors do, and those land as status: failed rows.
Check the IndexNow key file if submit_index_now is on. The scheduler skips submission with status skipped when the key isn't published at the storefront — see Setting up Autopilot rules → Cooldowns.

Reverting Autopilot fixes

Reverting is per-fix, not per-run. Each completed fix in the Fix Queue gets a "Revert" button (phase 247 backup ledger). Open the Reports → Health → recent fixes section, find the row, click Revert. The original Shopify value is re-applied via the same mutation path that placed the fix.

There is no "revert this whole Autopilot run" button — backups are stored per fix_queue row, not grouped by run.

Activity log retention

Rows are kept indefinitely (no automatic pruning). The CSV export is the recommended path if you need offline records — Shopify retains the underlying mutation history but won't surface it filtered to your app's actions.