Read automation logs and receipts

Logs are the source of execution truth

The builder describes intent. Runs records observed execution. Open a workflow and select the Runs tab. Do not diagnose from an error toast alone; use the run, ordered step trace, visible action outcome, and any pending resume together.

Narrow the investigation

Use the time range, status, search, trigger, owner, step, and failure-reason filters. Start with the smallest window around the reported event. The page supports statuses including success, partial, and failed, and groups failure reasons so repeated operational issues can be separated from one-off record data.

Investigate a reported failure

1. Open Automations, choose the workflow, and select Runs.
2. Set the time range and choose Failed or Partial.
3. Search with a safe identifier or select the relevant owner, trigger, step, or failure reason.
4. Expand the run that matches the approximate time.
5. Read the run status, duration, trigger context, published version, and ordered trace.
6. At the failed step, read its input summary, output summary, error, and receipt state.
7. Check the waiting-work panel for pending, running, failed, or cancelled resumes tied to the run.
8. Compare other failures in the same group before deciding whether the problem is configuration, data, connection health, or one record.

Interpret common patterns

• Skipped with a safety reason: the control may be working as designed; inspect suppression, quiet hours, caps, or journey eligibility.
• Partial: some steps completed and a later step did not. Never restart from the beginning without checking receipts.
• Uncertain receipt: WRKZY blocks an unsafe automatic repeat because the external outcome cannot be proved.
• Resume failed: the initial run reached a wait; the continuation failed later.
• Several workflows failing on one channel: inspect Settings delivery or the connected provider before editing every workflow.

Preserve and share evidence safely

Owners and Admins can use Export retained runs from the workflow menu when an operational review needs the retained dataset. Use Redact details when customer identity and step detail must be permanently removed; status, timing, version, and step outcomes remain for reporting. Redaction is irreversible.

For support, provide workspace slug, workflow name and ID, run ID, approximate time and timezone, published version, failed step label, receipt state, and redacted error. Never provide provider secrets, webhook keys, message bodies unrelated to the incident, passwords, or verification codes.

Expected result

You can state exactly what happened and whether a retry, individual wait recovery, provider fix, version rollback, or no action is appropriate.