About this block

Report Run History logs the recent runs of a scheduled report, MRR by plan, most recent first. A three cell summary strip carries the 30 day success rate at 94.6%, the median duration at 43s, and the last successful run at Jun 12, 08:00, with a Run now button in the corner. The table below lists seven runs with a status badge, start time, duration, row count, and the trigger that fired it, whether a daily schedule, a manual run by Maya Chen, or a deploy token over the API.

Runs are one typed array with a status union, so a failed run surfaces its error inline (a source connection timed out after ten seconds) and a running row shows a pulsing dot with a pending row count. The footer note that runs are retained for 90 days and failed schedules retry once before alerting the owner answers the two questions an operator asks first.

When to use

Reach for this block on the detail page of a scheduled report or pipeline, wired to your run log and retry policy. The Run now button should append a running row at the top that resolves in place when the run finishes.

A natural flow around it on an Application Pro page:

Before

• Scheduled reports table
• App shell

After

• Report builder
• Status health

What you can display

One strong use is a scheduled report run log. Other run histories of the same shape:

• Pipeline runs. ETL jobs with a stage count and the failed stage named in the inline error.
• Export history. File exports with a size column and a download link on each completed row.
• Sync runs. Integration syncs with records created, updated, and skipped in place of a single row count.

Tip: keep the inline error on the failed row itself, so an operator never opens a run just to read why it broke.