The following types of jobs can be executed in
|D s product|
- Transform job: This type of job executes the steps in your recipe against the dataset to generate results in the specified format. When you configure your job, any set of selected output formats causes a transform job to execute according to the job settings.
- Profile job: This type of job builds a visual profile of the generated results. When you configure your job, select Profile Results to generate a profile job.
- Publish job: This job publishes results generated by the platform to a different location or datastore.
- Ingest job: This job manages the import of data from a JDBC source into the default datastore for purposes of running a transform or sampling job.
For more information, see Run Job Page.
Identify Job Failures
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.
Jobs that Hang
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:
- Resubmit the job.
Try Other Job Options
You can try to re-execute the job using different options.
- Look to cut data volume. Some job failures occur due to high data volumes. For jobs that execute across a large dataset, you can re-examine your data to remove unneeded rows and columns of data. Use the Deduplicate transformation to remove duplicate rows. See Remove Data.
- Gather a new sample. In some cases, jobs can fail when run at scale because the sample displayed in the Transformer page did not include problematic data. If you have modified the number of rows or columns in your dataset, you can generate a new sample, which might illuminate the problematic data. However, gathering a new sample may fail as well, which can indicate a broader problem. See Samples Panel.
Download Error Report
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
- Login to the
as an admin or the user who created the job.
D s webapp
- Click the Jobs link in the left navigation bar.
- In the Jobs page, click the identifier for the job that failed.
- In the Overview tab, review the Failed Stages entry or entries.
- To acquire the error report, click Download error report. Review and forward the report as needed.
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
|D s support|
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.
Report an Issue
If you believe that your job has failed due to an issue with
|D s product|
|D s support|