Pipeline jobs

Long-running work may be represented by a job. The API surface includes pipeline status, cancel, and retry operations, and report-studio job operations. Use the operation schemas to determine the job identifier, status representation, and allowed transitions; this guide intentionally does not invent status names. See the Pipeline jobs API reference for exact request and response schemas.

A submitted or accepted job is not proof of completion. Poll the documented status operation, handle failure explicitly, and review generated artifacts before downstream use. Avoid retrying a job until you know whether the original completed.

The 17-phase workflow and compute boundaries are described in the Product Overview. The phase manifest is an internal implementation detail and is not linked from the public guide.