Find automation failures in the activity center

Administrators open Settings → Automation activity. Select a reporting window from 1 to 90 days, then filter by activity type or state. Results are paginated; use the page controls rather than assuming the first page is the full history. Refresh manually after an event or configuration change.

The summary shows failures, pending and overdue work, processing items needing review, unprocessed triggers, and rules with at least three failures in the selected window. Filters apply to both the list and summary. This is operational metadata, not a copy of customer message bodies or provider payloads.

An observed or processed trigger does not prove that a rule matched or a message was sent. Pending work is waiting for its due time or sending window; cancelled work was skipped, for example because a rule was paused, consent was missing, or the appointment changed. Open a record to inspect its reason and related identifiers.

Sent means the messaging provider accepted the request, not confirmed handset or inbox delivery. Processing work older than 15 minutes needs investigation. An interrupted request may already have reached the customer: check provider history before attempting another send.

The activity center is read-only. It does not retry, replay, activate rules or send messages. An authorized administrator-owned workflow MCP connection can use list_automation_activity and get_automation_activity with the same company boundary and reporting limits.