Background Job
What It Is
A background job gives long-running Rhythm work a continuing record. Staff can follow the work after the request that initiated it returns, even when the work crosses services or takes several minutes. Workspace preparation, search rebuilding and monthly snapshot production are examples. The record supplies a place to inspect what started, what completed and what needs recovery.
The job combines a declared kind of work with an individual execution identity. Its steps, attempts, progress and event history describe that particular run. The owning module defines the work and its consequences; the shared engine provides consistent recording. A submission identity connects repeated requests to the same intention. The governing submission and transition contracts are specified in the background-work capabilities.
What It Is Not
The durable job record is distinct from the cloud execution carrying out its tasks. An execution may disappear or fail before starting, while its job still needs an understandable outcome. A data import or bulk-edit run belongs to the separate Data Job Engine. Ordinary queued messages also serve a different purpose: they carry recoverable single tasks without becoming an operator’s multi-step progress record.
How It Is Used
Rhythm staff inspect jobs in HQ when preparing workspaces or investigating failures. A customer administrator uses Scheduled Jobs to review activity within the active workspace. These views answer related questions for different audiences: staff may investigate across customers, while customer readers work within their evaluated reach.
A useful job record lets someone distinguish unfinished work from failed work and identify the next recovery action. Reconciliation provides a second way to settle work when ordinary task reporting stops. Retry creates a new execution record rather than erasing the first attempt. A readable monitor therefore supports investigation after the person has left the original screen or the execution has stopped.
Its Facets
Kind. The declaration identifies the work, its owning application and the recovery behavior its owner supports. Readable labels make a mixed list understandable.
Step definition. The published catalog explains the sequence a person watches. It preserves the wording used for the run even when later declarations change.
Steps and attempts. These describe how execution progresses and whether a task has been attempted more than once. They help staff distinguish ordinary retry from final failure.
History. Numbered events provide the chronological account behind the current summary. Monitors can request events beyond their last position.
Outcome and consequence. The final status describes the job, while the registered consequence describes what failure means for its subject.
Requester notice. Selected work attempts to tell its requester how it ended. Delivery state is recorded separately, and the current mechanism admits duplicate delivery in interruption or concurrency cases.
Retry lineage. The connection between attempts preserves the recovery story and supports reuse of completed work.
Subject. A readable subject explains what the job concerns without asking staff to interpret internal references.
How It Relates
Jobs usually serve another module’s records: a workspace, search index, snapshot or population. Those modules retain the meaning of their work. Licensing uses jobs indirectly for authorization-cache invalidation. Compatible publishing views let jobs from other Rhythm services participate in the same monitors. Workspace purge applies the job-lifetime rules while preserving the record of the deletion itself.
What It Could Become
The product should decide which audiences may retry or cancel each declared kind. The engine’s support does not establish that a usable management surface exists. Requester links also need to follow the audience as customer-requested kinds adopt notices. A move to the notifications platform should retain delivery evidence while stating honestly whether the contract guarantees suppression of completed repeats or strictly once-only delivery.