View runs
See when a job ran, whether each run succeeded, and what your target answered.
Every run and each of its attempts is kept for 30 days. Use them to check that a job is working, and to find out why one failed.
See a job’s runs
- In the console, open the project, then Scheduler.
- Select the job. Its runs are listed under Runs, newest first.
- Select a run to see its attempts.
Run statuses
| Status | Means |
|---|---|
pending | Due, and about to be called |
running | We are calling your target now |
retry_wait | An attempt failed, and the next one is waiting for its time |
succeeded | Your target answered with a 2xx status |
failed | Every attempt allowed has failed |
cancelled | The job was paused before the run could finish |
Find out why a run failed
Open the run and look at its last attempt:
- The status code is what your target answered. A 5xx status means your app failed. A 4xx status often means the job sends something your app does not accept, such as a missing header.
- The error class says what kind of failure it was, such as
timeoutordns. See Why attempts fail. - The response shows the first 4 KB of what your target answered.
Missed runs
When a job misses some of its times, only the latest missed run happens. Its skippedBefore counts the others, and the console shows it as Missed before this run.
Last updated