Execution history
Qubit records every run of a scheduled task, whether you started it, its schedule did, or a webhook call did. To open the history, open Tasks in the sidebar and click View History on the scheduled task's row, or choose it from the row menu.
The history page
The header shows Execution History and the scheduled task's name. Edit opens the scheduled task in the builder.
The summary counts the runs listed on the page: Total Executions, Successful, With problems, Failed, and Average Time.
Recent Executions lists up to 50 runs, newest first:
- Status: the result of the run.
- Started At: how long ago the run started, with the date and time below it.
- Duration: how long the run took.
- Trigger:
manualfor a run started in Qubit,scheduledfor a scheduled run, orwebhook:followed by the caller's IP address.
| Status | Meaning |
|---|---|
| Pending | The run was created and has not started. |
| Running | The run is in progress. |
| Completed | The run finished and no step failed. |
| Completed with problems | The run reached the end, but at least one step failed and was set to continue after errors. |
| Failed | A step failed and stopped the run. The steps after it did not run. |
| Cancelled | The run was stopped before it finished. |
Run details
Click View (the eye button) on a row to open Execution Details:
- The status, start time, and duration.
- For a failed run, an Error box with the message. For a run with problems, a Finished with problems box. Failed at step gives the ID of the step.
- Step Results, with one row per step showing its status and duration. Steps are listed by their internal ID, such as
trigger-1. Click a row to see that step's error or output. - Final Output, the data the run ended with.
- How many insights, datasets, and alerts the run created, if any.
Failures
By default, a step that fails stops the run, and the run is Failed. A step can be set to continue after an error. The run then goes on and ends as Completed with problems.
A Failed run with the trigger scheduled and no step results means the schedule itself stopped, because Qubit could not read its cron expression or timezone. See Setting a schedule.
Qubit does not send a notification when a run fails. Check this page after you change a scheduled task or its schedule. For common causes of failed runs, see A scheduled task didn't run.
How long runs are kept
Qubit deletes run records older than 30 days.