Job executions

A job execution represents the outcome of running a job. It provides details about the tasks performed, the job's inputs and outputs, and its overall status.

Job Execution Status

A job execution can have one of the following statuses:

• PENDING: The job execution has been initiated but has not started yet. This may occur if the job is waiting for a specific pipeline to become available or for a scheduled start time.
• RUNNING: The job execution is in progress, and its tasks are actively being executed.
• COMPLETED: The job execution finished successfully, with all tasks completed without errors.
• USER_ERROR: The job execution ended with errors related to user inputs or outputs. Possible reasons include:
  • Invalid user inputs
  • Unauthorized actions, such as exceeding a quota when attempting to create a new item in a table.
• FAILED: The job execution ended with errors due to technical issues. This could be caused by problems in the job definition or unexpected technical errors within the Data Factory platform. Contact our support team for assistance in diagnosing and resolving such issues.
• TERMINATED: The job execution was stopped by the user before completion.
• TIMEDOUT: The job execution was automatically stopped because it exceeded the maximum allowed runtime.

The diagram above illustrates the possible transitions between the various job execution statuses.