The following statuses can be assigned to jobs:
| Job Status | Description |
|---|---|
| Abandoned |
A planner has decided that any work on the job is to be discarded (see Abandoning a Job). Once abandoned, a job is finished and cannot be re-allocated. Abandoned jobs do not progress any further, unless the planner wants to restart it using Retry. |
| Activated |
An allocated job has been claimed by a user and job extraction initiated. |
| Allocated |
Once a job has a name, type, and an allocated user or group, planners can set the job to be allocated. The job will then appear in the relevant user's Worklist ready to be activated. Jobs can be allocated when they are created (see Creating Jobs), or when editing them (see Allocating a Job). |
| Archived |
Jobs can be archived so that they are kept for record keeping but are otherwise not visible. This can either be performed on individual jobs (see Archiving a Job), or in bulk (see Archive Jobs). |
| Committed |
The job has passed reconciliation and validation, and the edits have been merged and applied to the live data and the publication database. |
| Completed |
The job has been archived and all associated resources cleaned up. |
| Conflicted |
Another user has made a change to a feature that has been modified or deleted since the job was initially activated. |
| Downloaded |
The job's data and metadata package has been downloaded by the user. This status implies that the user is currently editing the job. |
| Failed |
The job has failed and has no state to which to revert. An administrator will need to investigate what has happened to this job by examining the BPEL process logs. |
| Invalid |
The job's data changes have failed validation according to the defined business rules. A child job will have been created which contains the data and the list of validation failures. When the child job is corrected and submitted, this job will continue the workflow by trying to validate itself again. |
| Prepared |
A job has finished being activated, a workspace has been created, and a job package has been extracted or created, ready for download. |
| Proposed |
New jobs are created with a Proposed status if an editor and/or group is not defined, or if the planner has decided not to set the job status to Allocated. The job will not appear in users' Worklist until it is allocated. |
| Published |
After the job is committed to the live data, any optional downstream updates to publication databases occur. This status is reached after the downstream updates to publication databases are complete. Edits are applied to the publication database. |
| Quarantined |
The job has been selected to be manually inspected. This status is reached after the data has been uploaded and validated but before it has been committed. |
| Uploaded |
A user has made and saved edits, and uploaded them to the Worklist to be routed for reconciliation and validation. This status is reached when the job edits have been successfully written to the job's workspace but before any further validation is applied. |
