Types of Errors

This page lists information about errors that can occur when executing jobs.

Note: For a description of the errors returned by the HTTP API, see Protocols in the API specification. For a description of the errors returned by API bindings, see API bindings documentation.
The following table enumerates the possible categories of failure reasons that may occur (reported in the failureReason of a job's describe hash and visible in the monitor tab on the website).
Failure Reason Name
Example Failure Message and Explanation
​InputError​
"There was an error parsing the job's inputs, or one of its dependencies cannot be fulfilled"  In general, the message will mention the input field affected and the reason there was a failure.
​AuthError​
"The job can no longer be run because a launching authentication token has been revoked or expired"
​ExecutionError​
This occurs if there is an error encountered while attempting to run the executable on a worker in the cloud.
​AppError​
This error is reported by an executable, either through the local file job_error.json, or via a native exception.  The failure message is given by the executable.
​AppInternalError​
This error is reported by an executable, either through the local file job_error.json, or via an exception or exiting with a nonzero exit code.  The failure message is given by the executable.
​OutputError​
"There was an error parsing the job's outputs, or one of its dependencies cannot be fulfilled"  In general, the message will mention the output field affected and the reason there was a failure.
​UnresponsiveWorker​
"The machine running the job became unresponsive"  If the cloud worker running the job does not respond for a few minutes, the job fails.
​JobTreeFailure​
"<Other job ID> failed because of <other job's failure reason>: <other job's failure message>"  Once a job fails, it triggers this failure reason for all other jobs in the same job tree that have not yet entered a terminal state
​DependencyUnsatisfiable​
"<Other job ID> was a job dependency but failed"  This occurs if a job depends on a failed job in another job tree
​JMInternalError​
"The system encountered an internal error"  This error indicates that something unexpected happened while processing your job, and you will not be charged
​JobTimeoutExceeded​
"The job timeout <timeout_value> has been exceeded while executing <entry_point_name>"  In general, the message will mention the entry point at which the timeout was exceeded.

Docker Images

AppError

Last updated 7 months ago

Failure Reason Name	Example Failure Message and Explanation
InputError	"There was an error parsing the job's inputs, or one of its dependencies cannot be fulfilled" In general, the message will mention the input field affected and the reason there was a failure.
AuthError	"The job can no longer be run because a launching authentication token has been revoked or expired"
ExecutionError	This occurs if there is an error encountered while attempting to run the executable on a worker in the cloud.
AppError	This error is reported by an executable, either through the local file job_error.json, or via a native exception. The failure message is given by the executable.
AppInternalError	This error is reported by an executable, either through the local file job_error.json, or via an exception or exiting with a nonzero exit code. The failure message is given by the executable.
OutputError	"There was an error parsing the job's outputs, or one of its dependencies cannot be fulfilled" In general, the message will mention the output field affected and the reason there was a failure.
UnresponsiveWorker	"The machine running the job became unresponsive" If the cloud worker running the job does not respond for a few minutes, the job fails.
JobTreeFailure	"<Other job ID> failed because of <other job's failure reason>: <other job's failure message>" Once a job fails, it triggers this failure reason for all other jobs in the same job tree that have not yet entered a terminal state
DependencyUnsatisfiable	"<Other job ID> was a job dependency but failed" This occurs if a job depends on a failed job in another job tree
JMInternalError	"The system encountered an internal error" This error indicates that something unexpected happened while processing your job, and you will not be charged
JobTimeoutExceeded	"The job timeout <timeout_value> has been exceeded while executing <entry_point_name>" In general, the message will mention the entry point at which the timeout was exceeded.