Job Status and Lifecycle | emtelligent Documentation

Overview

When you submit a job to the Extract API, it progresses through a series of states that track its execution from submission to completion. Understanding these states helps you monitor job progress, troubleshoot issues, and know when outputs are ready.

Job Lifecycle

A successfully completed job progresses through these states in order:

Job Lifecycle

Job Statuses

Status	Definition	Description
`queued`	Job received and created
`ingesting`	Data validation	Downloading the documents from customer’s storage for processing
`validating`	Data ingestion	Validate source files against data contract. Validation starts after ingestion
`running`	Data processing and extraction	Pipeline has started
`completed`	Data ready for collection	Pipeline has completed and output is available for customer to collect. Customer should call /collect to upload output to their storage
`transferring`	Uploading outputs to customer storage	Uploading the output files to the customer’s s3 bucket
`transfer_completed`	Output files have been successfully transferred to customer storage
`transfer_failed`	File download/upload was interrupted before all files were transferred	An error occurred during the file transfer - For e.g. STS credentials expired
`failed`	Failure occurred during the data ingestion phase due to an authentication or data validation error	Authentication to the customer’s storage failed or one or more data contract requirements were not met. Fix and create a new job.
`cancelled`	Job was cancelled. Job can be cancelled if not completed or paused.
`paused`	Job was paused	Jobs can only be paused and resumed by System Administrator. If you wish to stop a job, you should call /cancel. Paused state allows for emtelligent personnel to investigate.

State Transitions

Job Transition

Job Status Polling

How to Check Job Status

Use the API endpoint to check the current status of your job:

curl -X 'GET' \
  'https://extraction-api.emtelligent.com/api/v1/jobs/<job_id>/status' \
  -H 'accept: application/json' \
  -H 'X-API-Key: <api-key>'

Response Example:

{
    "job_id": "<job_id>",
    "job_name": "<job_name>",
    "job_status": "running",
    "job_details": {
        "queued": {
            "pipeline_name": "<pipeline_name>",
            "pipeline_params": {
                "extraction_type": [
                    "labs",
                    "vitals"
                ]
            }
        },
        "extract": {
            "queued_at": "<date-time>"
        }
    }
}