Missed runs
A missed run is a scheduled report run that didn't execute. It's marked with a Missed status in the history.
Causes of a missed run
Inactive connection
The most common cause. The access token for the data source has expired or been revoked. While the connection is inactive, every scheduled run is skipped.
The previous run is still in progress
If the next scheduled run time arrives while the previous run is still in Running status, the new run is skipped. The system doesn't run parallel executions of the same report.
Destination sheet unavailable
The spreadsheet was deleted, the sheet was renamed or deleted, access permissions were revoked, or the spreadsheet is blocked by corporate policy.
Concurrent run limit
A workspace has a limit on how many reports can run at the same time. If the limit is reached and the queue wait time expires, the run is skipped.
DST (daylight saving time transition)
When clocks move forward, the scheduled run time (for example, 02:30) may not exist. The run is skipped.
Configuring missed-run behavior
The schedule settings offer two options:
Skip
A missed run isn't caught up. The next run happens as scheduled. The safest option for reports where data accumulation isn't critical.
Catch up
The system will attempt to run the missed run as soon as the cause is resolved. Rules:
- Only the most recent missed run is caught up
- If several runs in a row were missed, only one will execute
- Catching up doesn't shift the schedule — the next run still happens on schedule
- If the cause isn't resolved within 24 hours, the run is marked as permanently missed (Missed) and is not caught up
How to track missed runs
In the interface
- In the run history, missed runs are marked with a Missed status and shown in gray
- Hovering over the status shows the cause
- The report list shows a warning if there have been recent misses
Notifications (if configured)
You can configure notifications for missed runs: email on miss, in-app notification, or a webhook for integration with external monitoring systems.
How to verify
- Open the report's run history
- Check for any Missed statuses
- Hover over a Missed entry to check the cause
- If the cause is an inactive connection, refresh the token in the Integrations section
Prevention
- Regularly check connection status (Integrations section)
- Set up notifications for expiring tokens
- Enable Catch Up for critical reports
- Avoid scheduling run times during the DST transition window (02:00-03:00)
- Monitor the run history at least once a week
Related articles
- Disabling a schedule — a temporary pause
- Timezone — DST and missed runs
- Statuses — a description of all statuses
- Automatic runs — how automatic runs work