Run history and audit log

Last updated 25 August 2026

Every Auto-Pilot evaluation is recorded so automation is never a black box.

What each run records

- Timestamp and trigger that started the run.

- Rules evaluated and which matched.

- Subscriptions affected.

- Action taken, or the reason no action was taken.

- Outcome, including any error and whether it was retried.

Reading the log

Use it to answer three questions: did the rule fire, did it match what you intended, and did the action complete. A rule that fires but never matches is usually over-conditioned; a rule matching everything is usually missing a condition.

Retention and export

Run history is retained for your account's full lifetime and is included in a data export. Household administrators can see runs for shared subscriptions; personal subscriptions stay private to their owner.

Errors

Failed runs record the reason and are retried on a backoff schedule. Persistent failures raise a notification rather than failing silently.

Relationship to the audit log

Auto-Pilot run history covers automation on your own account. Privileged staff actions are recorded separately in an immutable administrative audit log that account holders do not have access to modify.

// STILL NEED A HAND?

We reply to every message, usually within a business day.

Contact support