Scheduled jobs

Scheduled jobs are the recurring background tasks the platform runs on a cadence — the maintenance and processing work that happens automatically rather than on demand. This area lets administrators oversee them.

The reason to surface background work to administrators at all is that silent automation is a liability in a regulated system. When a recalculation or a periodic check feeds compliance-relevant data, “it usually runs” isn’t good enough — you need to be able to confirm it did run, on schedule, and catch it when it didn’t. Making the job roster and its run history visible turns the platform’s automatic upkeep from an act of faith into something an administrator can verify, which is exactly the posture a dependable system of record requires.

What scheduled jobs do

Some work is best done on a schedule rather than in response to a click: recalculations, periodic checks, housekeeping, and other routine processing. Running these as scheduled jobs keeps the platform current without anyone having to trigger them, and concentrates that recurring work at sensible times rather than scattering it through the day.

Overseeing jobs

From here you can see the jobs that are scheduled, their schedule, and their run history — when each last ran and when it’s due next — so you can confirm the background work is happening as expected. A job that hasn’t run when it should is visible here rather than failing silently, which matters when downstream data depends on it.

Reliability you can verify

The point of surfacing jobs to administrators is accountability: the automated work that keeps the system healthy is something you can inspect and trust, not a black box. Where a job’s results feed compliance-relevant data, being able to confirm it ran is part of keeping the record dependable. Operational detail about job execution can be found alongside System logs.