Managing the Jobs page

The Jobs page provides details about all of the DQ Jobs with attempts to run. When a DQ Job runs, this is typically the first place you should check to track its status.

Note All times on the Jobs page reflect the UTC timezone.

Jobs Status Trend

The Job Status Trend is a graph that shows you details about the health of your DQ Job submission statuses over time. You can select the filter in the upper-right side of the graph to control the time period that displays.

Managing the Jobs table

The Jobs table is a list of all of the DQ Jobs with attempts to run. The Jobs table shows run details about the Job and lets you click a dataset to view its findings.

You can search for individual Jobs, filter the Jobs table by Job Status, and apply a Limit to control the number of past DQ Job runs that the list includes.

The following table shows the columns of the Jobs table.

Column	Description
Job Id	The automatically generated number that identifies a DQ Job as unique. You cannot edit the Job Id.
Agent Id	The identification number of your agent. Note Because Pushdown Jobs do not require an agent to process the Job, the Agent Id is always 0.
Dataset	The name of your dataset.
Status	The completion status of your DQ Job. Use the Job Status filter to filter by statuses as they appear in this column. These statuses include: Status Description Running DQ Jobs that are currently processing the various runtime activities. Finished DQ Jobs that have completed all activities and whose results are available. Failed DQ Jobs that have not completed due to a critical event in one of the runtime activities. Submitted DQ Jobs that are in the Staged (to run) activity. While this typically means that the DQ Job will run once its turn in the Jobs queue arrives, it may also indicate a problem with the agent or another exception if it takes an abnormally long time to progress beyond Staged. If this occurs, check the Exception column and Job logs for any unusual events, such as an exception or a fatal error. Common unusual events include: Insufficient resources allocated to the compute pool preventing the agent from processing the Spark job. An incorrect or incomplete DQ Job query. One of the data models is using too many workers to run a part of the DQ Job. This is especially common for complex rules, including @t1 rules. If the issue is Job-related, we recommend editing the DQ Job and reducing its scope. For example, you can limit the number of rows included in the DQ Job. If the issue is related to infrastructural processing elements, we recommend allocating more memory or threads to the agent to allow the DQ Job to run more efficiently. Unknown DQ Jobs whose statuses are not explicitly defined by Data Quality & Observability Classic. This can include DQ Jobs that timed out because a given runtime activity took too long to process, failed to load a table, failed to connect to an offline or misconfigured driver pod. or DQ Jobs whose agents have crashed. Common unusual events include: Insufficient resources allocated to the compute pool preventing the agent from processing the Spark job. An incorrect or incomplete DQ Job query. One of the data models is using too many workers to run a part of the DQ Job. This is especially common for complex rules, including @t1 rules. If the issue is Job-related, we recommend editing the DQ Job and reducing its scope. For example, you can limit the number of rows included in the DQ Job. If the issue is related to infrastructural processing elements, we recommend allocating more memory or threads to the agent to allow the DQ Job to run more efficiently.
Activity	The task that the system performs while it processes the DQ Job.
Start Time	The timestamp when the DQ Job starts to run. The format is YYYY-MM-DD HH:MM:SS.
Update Ts	The timestamp of the last processing activity. The format is YYYY-MM-DD HH:MM:SS.
Job Exception	When an error or exception occurs, a helpful description of the event displays in this column.
Username	The username of the person in your organization who ran the DQ Job.
Actions	The action you can take to troubleshoot or terminate your DQ Job.

Tip Click next to the Limit filter to refresh the Jobs table. Sometimes this is helpful to monitor the activity changes and track the status of a DQ Job.

Exporting details from the Jobs page

You can click to export the details of the Jobs table to the following formats:

• CSV
• Excel
• PDF
• Print