Run History Table
Automation execution log with timestamp, automation name, status badge, duration, items affected, and inline error text on failed rows.
Automation execution log with timestamp, automation name, status badge, duration, items affected, and inline error text on failed rows.
Search blocks by description or jump to a page.
The source for every Application block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Run History Table is the execution log for all automations, six rows spanning two days: timestamp, the automation expressed as trigger arrow action (Deal won to Slack #sales-wins, Invoice overdue to Reminder email), a status Badge (success in secondary, failed and skipped in outline), duration in tabular-nums, and items affected. The failed row at Jun 13, 11:30 expands into an inline error sub-row: Mailgun API returned 422: recipient address is not verified in sandbox mode. A footer note states the retry policy: failed runs retry up to 3 times with exponential back-off before alerting.
Runs are one typed array; the badgeVariant lookup maps RunStatus to the two badge variants so no conditional logic sits in JSX. The inline error sub-row is a second TableRow keyed by run id plus the suffix -error.
Reach for this block on the automation detail or workspace run log page, wired to your run history endpoint paginated by date range.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the cross-automation run log. Other history table configurations:
Tip: inline error text next to the failed row removes the need to open a details panel for the most common debugging case.