In the Jobs page, you can track the status of all of your jobs.
Jobs can be initiated from:
Each job listed in the Jobs page is a grouping of related jobs acting on the same recipe and dataset(s). Each of these jobgroups breaks down into one or more of the following job types.
Tip: To review the status of individual jobs within a jobgroup, hover over the icons in the Status column for the jobgroup.
Even when selected, profiling jobs may not appear in the Jobs page. In some cases, a profiling job may be folded into a transform job for optimization reasons.
NOTE: When the profiling job is run as part of the transform job, there is no listing for profiling in the mouse-over popup.
P ublish: Depending on multiple factors, your job may include a second Publish job that occurs after the Transform job. For example, jobgroups can include internal Publish jobs for writing results to the designated location in the base storage layer.
Publishing can also be executed as a separate, post-execution job. As needed, job results can be published from their target location to another location or data store. These jobs are tracked separately as Publish jobs and can be launched from the Job Details page. For more information, see Job Details Page.
Ingest: For larger datasets from some relational connections, the transfers the data from the source to the default storage layer for faster processing. These ingest jobs occur before any transform or profiling takes place.
Tabs and Statuses:
Each of the available tabs corresponds to a possible status for jobs that have been initiated on the platform.
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.
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.
Queued: Job has been queued for execution.
You can review and drill into any job that you initiated.
You can also drill into any job that was initiated from a flow that has been shared with you.
Administrators can review read-only listings for jobs created by other users.
User: The that initiated the job.
Started: Start timestamp for the job.
Search: Enter text in the search field to filter the listed jobs by job ID, flow name, or dataset name. You can also filter by username.
Next to the job listing, click the options menu to see the following:
Export dependencies as Flow: For any job that you executed, you can export a snapshot of the flow, including all dependencies required to generate the job. This export can be useful for recording the state of the flow for job runs.
NOTE: An administrator may need to enable this feature in your environment. For more information, see Miscellaneous Configuration.
Delete job: Delete the job from the platform.
Deleting a job cannot be undone.
NOTE: This feature may not be enabled in your instance of the platform. For more information, please contact your . See Miscellaneous Configuration.
To filter the list of jobs based on dates or source of execution, click the Funnel icon. You can use the following dialog to filter the display of jobs.
Filter Jobs dialog
Show jobs based on the following available options:
Show all jobs
Only show manual jobs
Only show scheduled jobs
Only show CLI jobs
Start Betweenfrom the drop-down list and populate both date-time rows.
Ended Betweenfrom the drop-down list and populate both date-time rows.