The Errors page is a triage surface for automation failures — every action that errored, grouped by root cause, with retry tools and quick fixes. It's where you start when something's broken and you don't know what.
Where to find it
Go to https://app.trustpager.com/auto/errors. The page is organised by error category, then by automation, then by individual run. Recent failures are at the top.
Common error categories
- Integration token expired — an OAuth-based integration (Gmail, Google Calendar, Stripe, Xero, DocuSign) had its access revoked. Reconnect at https://app.trustpager.com/auto/integrations to clear.
- Provider error — the external service returned an error. The exact message is shown — Stripe's payment errors, Xero's validation errors, etc.
- Missing data — the automation needed a field that wasn't set (e.g. a contact with no email, an opportunity with no amount). Fix the source data or update the automation to handle missing values gracefully.
- Template error — a merge token referenced a field that doesn't exist or is null. The exact token is shown.
- Permission denied — the API key or user running the automation doesn't have the scope required. Update the role at https://app.trustpager.com/settings/permissions.
- Rate limit — an external service throttled us. Usually transient — TrustPager retries automatically.
- Validation — input failed schema validation. The exact field and reason are shown.
Triaging a category
Click any error category to expand it. You'll see:
- The number of affected runs in the last 24 hours, 7 days, and 30 days
- A representative error message and stack trace
- The most-affected automations
- Suggested action — usually a single click to fix the root cause
Many errors fall into a single root cause that resolving will clear hundreds of failed runs at once. Always look at the category-level fix first before diving into individual runs.
Retrying runs
For runs that failed due to a transient issue (provider outage, expired token, rate limit) and are now ready to succeed, click Retry all on the category to re-run every affected automation against the same source data. Or retry individual runs from the run detail.
Dismissing errors
Some errors are expected — for example, an automation deliberately tries an integration that's optional, and the failure is acceptable. Click Dismiss on the run to remove it from the active errors view without retrying. Dismissed errors are still visible in the full automation logs at https://app.trustpager.com/data/automation-logs.
Notifications for new errors
Configure agent alert rules at https://app.trustpager.com/auto/agent-alerts to get notified when error counts spike — you'll catch issues before clients notice. See https://trustpager.com/help-center/how-to-set-up-agent-alerts for details.
