Background jobs and schedules

Work that runs without somebody watching it, and how to tell whether it ran.

Some work does not belong in a screen: a nightly import, a revaluation, a statement run, a re-forecast. Those are jobs, and a job that should happen regularly is a schedule.

• A schedule names a job, when it should run, and what it should run against. The next due time is computed by the platform, not guessed by the browser.
• Every run is a row: when it started, how long it took, what it produced, and the error if there was one.
• A run in progress is claimed, so the same schedule firing twice does not run twice — a retried or overlapping trigger is refused rather than duplicated.
• The job library on the Batch Console opens on a tile per module with how many jobs it has, and says how many are cataloged but not built yet. Press a tile to list that module’s jobs, or Everything to list them all.