Job executions

A job execution is the result of the execution of a job. It contains information about the tasks that were executed, the inputs and outputs of the job, and the status of the job.

Job execution status

A job execution can have one of the following statuses:

• PENDING: The job execution has been triggered but has not started yet. The reason for this status can be that the job execution is waiting for a given pipeline to be available, or that the job execution is waiting for a specific time to start.
• RUNNING: The job execution is currently running. The tasks of the job are being executed.
• COMPLETED: The job execution has been completed successfully. All tasks have been executed without errors.
• USER_ERROR: The job execution has been completed with errors. The errors are related to the user inputs or the user outputs of the job. There are many reasons for this result:
  • The user inputs were not valid
  • The job attempted to perform an action that was not authorized, such as creating a new item in a table when the quota for that table had been reached.
• FAILED: The job execution has been completed with errors. This status most certainly indicated that a technical error occurred during the execution of one of the tasks of the job. The error may be linked to the definition of the job, or be due to an unexpected technical error within the Data Factory platform. Our specialized support team is available to help you diagnose and fix issues you may encounter.
• TERMINATED: The job execution has been terminated by the user. This status is used when the user decides to stop the execution of the job before it is completed.
• TIMEDOUT: The job execution has been terminated because it tooks too long to complete. This status is used when the job execution has been running for too long and has been automatically stopped by the platform.

The diagram above shows the possible transitions between the different statuses of a job execution.