The job states outlined below provide visibility into the job lifecycle, allowing you to identify areas that need attention or further action quickly.

1. Parked (Ul), PENDING (API) optional
   → Data uploaded to the work queue, awaiting processing.

2. Queued (UI), SCHEDULED (API)
   → Ready for processing; automatically managed based on app concurrency settings.

3. Processing (Ul), IN_PROGRESS (API)
   → Data actively being processed.

4. Needs Work (Ul), NEEDS_WORK (API)
   → New state explicitly outlining that the job is awaiting collaborator action. Triggered only when the "Verify Results" supertask is active.

5. Complete (UI), COMPLETED (API)
   → Processing is complete, and the output is ready. If applicable, this includes pending post-processing steps (see next).

6. Post-processing (Ul), POST_PROCESSING (API)
   → Jobs transition to this state if any of the following conditions are met
   • Redaction is configured for at least one field.
   • At least one validation rule is configured for a field or table column.
   • At least one field is of type 'Calculated' or 'Expression'.
   • At least one table header is of type 'DB Key' or 'DB Column'.

7. Post-Processed (Ul), POST_PROCESSED (API)
   → Post-processing completed; final output ready.

8. Needs Review (Ul), NEEDS_REVIEW (API)
   → Jobs transition to this state when specific conditions outlined in the Review Settings are met, including:
   • At least one validation rule failed
   • Low confidence of a field of table
   • Required field is blank
   • Specific tag assigned

9. Reviewed (Ul), REVIEWED (API)
   → This final job state is reached or reviewer clicks "Confirm" in the Data Review Ul or a request is sent to the jobs/review API endpoint (learn more here).

Terminal States (No Output Provided):

• Failed (Ul), FAILED (API) → Job encountered an issue.
• Expired (Ul), EXPIRED (API) → Processing exceeded the allowed time.
• Canceled (Ul), CANCELED (API) → Processing was stopped manually.