NOTE: If your job failed, you may be prompted with an error message indicating a job ID that differs from the listed one. This job ID refers to the sub-job that is part of the job listed in the Job summary.
You can review a snapshot of the results of your job.
Job ID: Unique identifier for the job
Tip: If you are using the REST APIs, this value can be used to retrieve and modify specifics related to this job. For more information, see API Reference.
- Job status: Current status of the job:
Queued:Job has been queued for execution.
Running:Job is in progress.
Completed: Job has successfully executed.
NOTE: Invalid steps in a recipe are skipped, and it's still possible for the job to be executed successfully.
Canceled:Job was canceled by user.
Failed:Job failed to complete.
NOTE: You can re-run a failed job from the Transformer page. If you have since modified the recipe, those changes are applied during the second run. See Transformer Page.
- Flow: Name of the flow from which the job was executed. Click the link to open the flow. See Flow View Page.
- Output: Name of the output object that was used to define the generated results. Click the link to open the output. See Flow View Page.
Optionally, you can turn your generated results into new datasets for immediate use in
|D s product|
NOTE: If you generated results in Parquet format only, you cannot create a dataset from it, even if the Create button is present. This is a known issue.
NOTE: When you create a new dataset from your job results, the file or files that were written to the designated output location are used as the source. Depending on your backend datastore permissions are configured, this location may not be accessible to other users.
Tip: To open the full flow, you can click its name in the upper-left corner.
Data sources tab
NOTE: If a flow is unshared with you, you cannot see or access the datasources for any jobs that you have already run on the flow. You can still access the job results. This is a known issue.
If your flow references parameters, you can review the state of the parameters at the time of job execution.