Platform capability · Background Jobs
Jobs that keep their state, report progress, retry and can be cancelled
A shared job engine for bulk import and export, reports, batch processing, scheduled tasks and your own job types. Every job goes through the same states, reports progress and follows the retry policy you set. A job that still fails after its retries is kept so it can be reviewed and run again. Each job handler receives a key that makes a retry safe, and must use it.
Bulk export, bulk import, reports, batch recalculation, scheduled clean-up and syncs with other systems are all background jobs. They share the same states, the same retry rules and the same monitoring. You declare a job type in the app declaration. The engine handles queuing, running, progress and notification.
Each job handler receives a key that identifies the job run. The handler uses it to avoid applying the same change twice when a job is retried. Data export jobs also save their position in the data and the state of the uploaded file. A paused or interrupted export resumes from the last saved position and does not start again.
Each customer has its own job queue and its own limit on jobs running at once. One customer starting ten exports does not hold up another customer’s scheduled report. Limits are set in the plan and enforced by the scheduler.
A solution architect will demo the live service against your domain model.