Job rejected by the preflight check

​

Issue

A job ends with the status Rejected in Unstructured Pipelines, or REJECTED in the API. The job processed no documents. In Unstructured Pipelines, the job’s Details tab lists one row for each rejected node under the message Preflight checks failed. Fix the errors below and retry.

​

Causes

A node in the workflow failed the Job Preflight Check with one of these results: Other check results, such as Network unreachable or Rate limited, do not reject a job.

​

Solutions

1. Find the nodes that failed the check:
   • In Unstructured Pipelines, open the job, and then read the Details and Errors tabs. For details, see Investigate a rejected job.
   • In the API, call the get job details endpoint, and then read failure_category and failure_reason for each node. For details, see Find why a job was rejected.
2. Fix each node based on its category:
   • Invalid credentials (AUTH_INVALID_CREDENTIAL): Check the connector’s or node’s keys, secrets, and tokens for typos, and replace any that expired or were revoked. For more fixes, see Authorization and permissions issues.
   • Permission denied (AUTH_PERMISSION_DENIED): In the source, destination, or model provider, grant the credentials the permissions that the connector or node needs. For more fixes, see Authorization and permissions issues.
   • Invalid configuration (CONFIG_INVALID): Check the connector’s or node’s names, paths, and URLs, and confirm that each referenced resource exists. For more fixes, see Configuration and resource issues.
3. Run the workflow again. Unstructured does not retry a rejected job. Each run creates a new job.

​

Additional resources

• To turn off the check for a workflow, see Jobs that skip the preflight check.
• To ask questions or get additional help with this issue, see requesting support.