Finalize a batch job
/lang2fhir/batch/{job_id}/finalizeSeals the job's item set and starts processing. Takes no request body. Finalize is idempotent: a retried finalize succeeds again.
If a previous upload did not complete, finalize returns a 409; re-send
the missing upload (with the same request_id), then finalize.
Finalizing a job with no items is a 400.
Path parameters
Job finalized and processing started
Response fields
Server-assigned job identifier.
The idempotency token supplied at create, if any.
Job status. completed means every item has finished — some may have
failed, so check counts for the split. failed is a whole-job
failure (the job could not run at all), distinct from individual item
failures, which never fail the job. canceled is a caller-requested
cancellation via POST /lang2fhir/batch/{job_id}/cancel; like the
other terminal states it keeps any results already produced readable
for the retention window.
pendingprocessingcompletedfailedcanceledWhether the job's item set has been sealed.
The sealed item count. It is 0 until the job is finalized, so an upload response always reports 0; poll the job after finalize for the real count.
A whole-job failure. Present only on a failed job.
When the job finished. Absent until then.
When the job and its stored inputs and results are deleted. Set 7
days out, with the clock restarting when the job reaches completed,
failed, or canceled. At expiry the job's request_id is freed for reuse.