Admin Scheduled Jobs: Cron Run History

Check whether a background job ran, how long it took and whether it failed: filter your organization’s cron run history by job, status and date on Admin → Scheduled Jobs.

Some work in Docklify happens on a schedule in the background — nobody clicks a button, the job simply runs when its time comes. Admin → Scheduled Jobs is where you check on those runs afterwards: each run leaves one row with when it started, how long it took, whether it succeeded or failed, a short summary of what it did, and the error message if it failed. The page only shows your own organization’s runs. Only Owner and Admin roles can open it.

Step 1: Open the run history and read a row#

1. Open Admin → Scheduled Jobs (/admin/cron-runs). The run list loads on its own — there is nothing to start or configure here.
2. Pick any row and read it left to right: start time, job name, duration, status, summary, error.
3. If the list is long, use the pager at the bottom of the table to walk through it — the page shows 50 runs at a time by default.

• Started is the moment that run began, shown down to the second — use it to match a run to the time something was supposed to happen.
• Job is the name of the scheduled job, shown exactly as the system names it.
• Summary is a short list of what the run produced — counts and results in plain key-and-value form. Long summaries are cut off in the table, so treat the row as the headline, not the full report.
• Error is empty (a dash) on runs that did not fail. On a failed run it shows the error message, cut off in the table — hover over it to read the full text.

One row is one run — not one job. The same job appears again every time it runs, so a healthy job builds up a long trail of rows over the days. When you scan the table on Admin → Scheduled Jobs, you are really reading that trail: recent rows at the time you care about, in the order the table gives you after filtering.

Step 2: Filter by job, status and date#

1. In the filter card above the table, pick a Job — or leave it on All to see every job together.
2. Pick a Status if you only care about one kind of outcome — for example Failed, to only see runs that went wrong.
3. Set a From and To date to narrow the list to a time window — one night, one week, whenever the problem was noticed.
4. Click Search. The list reloads from the first page with your filters applied.

The job picker on Admin → Scheduled Jobs lists the scheduled jobs that report runs for your organization — employee-term-sweep, abc-analysis and sequence-runner. Picking one is the fastest way to answer “has this particular job been running lately?”: if its rows keep appearing on schedule with Success, it has.

Step 3: Read the status and the duration#

• success (green) — the run finished and did its work.
• failed (red) — the run stopped with an error. Read the Error column on the same row before doing anything else.
• running (yellow) — the run has started and has not finished yet. Check again in a little while; a finished run flips to success or failed.
• Duration is shown as seconds, or as minutes and seconds on longer runs (for example 2m5s). A dash means the run has no recorded duration yet — typical while it is still running.

Read status and duration together. A success that suddenly takes ten times longer than its usual runs is worth noting even though it passed, and a failed run with a very short duration usually stopped early — the error text on that same row will say where. Comparing a run with the same job’s earlier rows on Admin → Scheduled Jobs is the quickest way to spot either pattern.

Step 4: Check on a job you suspect did not run#

1. Filter by that job and set the date window to when it should have run, then click Search.
2. No row at all in that window means no run was recorded for that time — the job did not run, or did not report a run.
3. A row with failed means it did run and hit a problem: copy the job name, the start time and the full error text (hover to see it all) — that trio is what support will ask for.
4. A row still on running long after it started is worth a second look later — refresh the search and see whether it has flipped to success or failed.

Docklify features used in this article#

• Cron run history for your organization (started / job / duration / status / summary / error) — Admin → Scheduled Jobs (/admin/cron-runs)
• Run filters by job, status and date range, with Search — Admin → Scheduled Jobs (/admin/cron-runs)
• Status reading at a glance (running / success / failed, color-coded) — Admin → Scheduled Jobs (/admin/cron-runs)
• Full error text on failed runs (hover the Error cell) — Admin → Scheduled Jobs (/admin/cron-runs)