Skip to main content
GET

Path parameters

string
required
The unique identifier of the job.

Response

string
required
Unique identifier for the job.
string
required
Document processing outcome. One of: SCHEDULED, IN_PROGRESS, SUCCESS, COMPLETED_WITH_ERRORS, STOPPED, FAILED, REJECTED. A REJECTED job failed the Job Preflight Check and processed no documents. A completed job can remain IN_PROGRESS briefly while counts settle.
array
required
Per-node processing statistics. Each object includes node_name, node_type, node_subtype, ready, in_progress, success, and failure counts.For a REJECTED job, each object also reports the result of the Job Preflight Check for that node:
  • failure_category: The stable category of the check failure. Use this value to decide what to do next. Treat a value that is not listed in the following table as UNKNOWN.
  • failure_reason: Human-readable detail about the failure, forwarded from the provider. Show this text to a person. Its format can change, so do not parse it.
Both fields are null for a node that passed the check.
string
Additional status message, if available.
object
Aggregate document counts: total_docs, total_docs_succeeded, and total_docs_failed, when available.
object
Advisory snapshot of current progress and other active jobs. Use processing_status for the final outcome.
array
IDs of jobs using workspace concurrency slots when this job was queued. This snapshot is not a current list of blockers.
string
Reason a completed job delivered no documents, if detected: NO_DOCUMENTS_DISCOVERED or NO_DOCUMENTS_SUCCEEDED.