Oversee scheduled jobs
See the recurring background work the platform runs on a cadence, confirm each job is running on schedule, and treat that automated work as something you can inspect rather than a black box.
Scheduled jobs are the recurring background tasks the platform runs on a cadence — recalculations, periodic checks, housekeeping, and other routine processing that happens automatically rather than on demand. This area lets you oversee them, so the work keeping the system current is something you can confirm rather than assume. For the reference, see Scheduled jobs.
See what’s scheduled
Some work is best done on a schedule rather than in response to a click; this is where that work is visible.
Before you start Open Administration and go to Scheduled jobs. You'll need administrator access.
- Review the jobs that are scheduled and the schedule each runs on.
- Note what runs automatically — recalculations, periodic checks, and housekeeping — rather than waiting on someone to trigger it.
Result Visibility into the automated work running behind the scenes. See Scheduled jobs.
Confirm jobs are running
A schedule only helps if the jobs actually run, so the run history is what you check.
- Review each job's run history — when it last ran and when it's due next.
- Watch for a job that hasn't run when it should have; here it's visible rather than failing silently, which matters when downstream data depends on it.
Result Confidence that the background work is happening as expected — and an early signal when it isn't.
Note Surfacing jobs to administrators is about accountability: the automated work that keeps the system healthy should be 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 sits alongside System logs.
Where to go next
For the operational logging that records how jobs and other system processes actually executed, see System logs.