ExecutionsEdit this page »
Executions track a single run of your monitored tasks.
Each time your application's task scheduler kicks off a task, a new execution record will be created.
A healthy execution lifecycle will start by the tasks next scheduled start time and finish within the tasks allowed runtime.
Note that a configurable grace period is added to the scheduled task's next start time to prevent false alerts due to network latency or simultaneous job delays.
Execution lifecycles that exceed the allowed execution run time will be considered to have timed out.
Tasks that are scheduled in your
unless() truth test constraints may finish in a healthy, but skipped state.
An execution can exist in one of five statuses: