The following types of jobs can be executed in :
For more information, see Run Job Page.
When a job fails to execute, a failure message appears in following locations:
The following is an example from the Jobs page:
Publish job failed
In the above example, the Transform and Profile jobs completed, but the Publish job failed. In this case, the results exist and, if the source of the problem is diagnosed, they can be published separately.
In some cases, a job may stay in a pending state indefinitely. Typically, these errors are related to a failure of the job tracking service. You can try to the following:
You can try to re-execute the job using different options.
When a job fails, you can download an error report, which can be useful for diagnosing issues:
Tip: If you are filing a request with , please be sure to include this error report. Additionally, please provide the information available in the About > Report issue dialog.
For each job in the failing job group, the error report contains:
The internal job identifier within the workspace where the error occurred. This value matches the job ID that is displayed in the
The identifier of the workspace where the error occurred
The ID for the specific job in the job group. These jobs can include sampling, profiling, transformation, writing results, ingesting data, and more.
|The internal identifier of the user within the workspace|
The status of the job, such as "Failed", "Completed", "Pending".
|errorMessageId||The ID of the error message that is shown in the UI.|
|errorTimestamp||Timestamp of the job failure. Not included if no error occurs for the job.|
|uiErrorMessage||Error message that is shown in the job UI. Not included if no error occurs for the job.|
If you are unable to diagnose your job failure, please contact .
NOTE: When you contact support about a job failure, please be sure to download and include the entire zip file, your recipe, and (if possible) your dataset.