See what an automation actually sent (Runs tab)

The Runs tab in Automations is the receipt trail for the whole automation engine: one row per message it queued, with a status chip, the recipient, the sending number, and a plain-English reason for anything that didn't send. When someone asks "did the customer actually get the reminder?" this is where you look. Click any row to see the exact message body and a timestamped timeline of what happened.

Reading the table

Columns: Workflow, Status, Recipient, From, Scheduled, Reason, Actions. The status chips mean:

The table refreshes itself every few seconds, and the Refresh button forces an immediate re-pull.

Filtering and searching

• Status pills across the top — All, Pending, Sent, Delivered, Failed, Skipped, Cancelled, Replaced — narrow the list to one status.
• The workflow dropdown (All workflows) shows a single automation's runs.
• The phone search box finds every run for one customer — type at least three digits of their number.
• The Overview tab's alert chips (like failed runs in the last 24 hours) deep-link here with the matching filter already applied.

Inspecting a run

Click a row to expand it. Three panels appear:

• Message — the exact text body, with every placeholder already filled in.
• Context — the entity it belongs to, the customer phone, the job source, the sender strategy, and the attempt count.
• Timeline — timestamped events from queued to sent (or skipped/failed), including any retries.

Retry and cancel

• Failed and Skipped runs show a retry button in the Actions column — fix the underlying cause first (for example, add the missing review link), then retry. A success toast confirms "Run queued for retry".
• Pending runs show a cancel button — use it to stop a message you don't want going out. The row flips to Cancelled.

Common Reason column messages

• "Deferred (quiet hours)" — rescheduled to after your quiet window (quiet hours).
• "Customer opted out" — the customer texted STOP; they can't be auto-messaged.
• "No review link for this job" — add a review link to the job source (how).
• "Sender number not ready" — the number is still completing SMS verification (fix).
• "Customer replied — stopped" — Stop on Reply ended the chain; a human owns the conversation now.
• "Job has no scheduled date" — the reminder had nothing to anchor to.
• "Automation turned off" — the workflow was disabled between queueing and sending.
• "SMS limit reached" — your plan's SMS allowance for the period is used up.
• "Phone can't receive texts (landline)" — the destination is a landline.

Troubleshooting

• The tab is empty — the empty state explains it: "Runs appear here as automations are triggered by real events." Nothing has fired yet; check that at least one workflow shows the Active badge on the Workflows tab.
• Lots of Skipped rows — usually healthy: opt-outs, quiet hours, and stop-on-reply all record as skips so nothing is hidden. The Overview tab only raises an alert chip when skips spike.
• A run shows Failed repeatedly — expand it and read the Timeline panel; each attempt is recorded with its error. If the error names the sender number, verify it in SMS status.