Review background jobs
As a workspace admin, check the history of ClaimDS background jobs — the scheduled processes that run behind the scenes — and read their error logs when something needs attention.
Some of ClaimDS runs on a schedule, behind the scenes. The background-jobs history is how an admin confirms that work is happening on time — and, when something slips, reads exactly what went wrong rather than guessing.
A health log, mostly boring
A healthy background-jobs history is uneventful: runs completing on schedule. Its value is on the rare day something fails — the error log turns "something feels off" into a specific cause you can act on or escalate.
Check the history
Follow the numbered steps below. This is an admin-only view; if you can't reach it, see fixing access errors.
Step-by-step
Open the background-jobs history
From the admin area, open the background jobs (cron runs) history. ClaimDS runs scheduled processes behind the scenes; this is the record of when each ran and how it went.
Scan recent runs
Look at the recent runs to confirm the scheduled work is happening on time. A healthy history is mostly uneventful — runs completing as expected.
Open a failed run's log
If a run failed, open it to read its error log. The log tells you what went wrong, so you can decide whether it self-corrects on the next run or needs a hand.
Confirm the next run
After a hiccup, check that the following scheduled run completed cleanly. Most transient issues clear on their own; the history is how you confirm rather than assume.
Escalate if a job keeps failing
If the same job fails repeatedly, that's worth raising with us — capture the job and the error from the log so it can be looked into quickly.
Frequently asked
What kind of work runs as a background job?
Scheduled, behind-the-scenes processing that keeps the workspace current. You don't trigger these by hand; the history just lets you confirm they're running and healthy.
Who can see the background-jobs history?
It's an administration view, limited to the most privileged roles. If you can't see it, you likely don't have an admin role in this workspace.
Still stuck?
Book a demo and we'll walk through it on your own data — or just talk to us.