The automation logs page shows every time an automation actually ran — every action that fired, was skipped, or failed. This is your debug surface for any automation that didn't behave as expected.
Where to find it
Go to https://app.trustpager.com/data/automation-logs. The same view is also available scoped to a single automation from the automation's detail page at https://app.trustpager.com/auto/automations.
Reading a run
Each row is one automation run, showing:
- Which automation fired
- What triggered it (record + event)
- Run status — succeeded, partially succeeded, failed
- Number of actions that ran vs total
- Duration
- Timestamp
Click any run to expand it and see the action-by-action breakdown:
- Each action with its result (success, skipped, error)
- Inputs the action received (with merge tokens resolved)
- Outputs returned
- Error messages if something failed
Common run statuses
- Success — every action ran without error
- Partial — some actions ran, others were skipped (often because a condition didn't match) or failed (an external service errored)
- Failed — the run errored before any actions could complete
- Cancelled — the run was queued and an auto-cancel rule dropped it (see https://trustpager.com/help-center/how-to-use-dispatcher for cancel rules)
Re-running a failed run
For automations that failed due to an external issue (provider outage, expired API token, etc.), you can re-run from the run detail. Click Re-run — TrustPager will execute the same automation against the same record, with the same input data.
Filtering
Filter by automation, status, date range, or the record that triggered the run. To find every run for a specific contact or opportunity, open that record and look at its activity feed — automation runs are linked there directly.
Errors page vs logs
The errors page at https://app.trustpager.com/auto/errors is a curated view of just the failures, with retry tools and root-cause hints. Use the automation logs to inspect any run; use the errors page to triage what's broken right now.
Retention
Run logs are retained for 90 days. Critical metadata (run status, action counts) is preserved indefinitely for reporting purposes.
