Managing executions - Data360_DQ+ - Latest

Data360 DQ+ Help

Product type
Software
Portfolio
Verify
Product family
Data360
Product
Data360 DQ+
Version
Latest
Language
English
Product name
Data360 DQ+
Title
Data360 DQ+ Help
Copyright
2024
First publish date
2016
ft:lastEdition
2024-07-09
ft:lastPublication
2024-07-09T15:09:58.774265
Tip: For an introduction to executions, see Executing data stages.

All users who have Read permission to a data stage can view the execution history for the data stage, see Executing data stages. As an Administrator, it can also be useful to track data stage executions across an entire environment in order to know when a dependent stage can be executed or used.

  1. Sign in as an Administrator, and select the environment for which you want to view the execution history for all executable data stages.
  2. From Admin menu at the top of the page, select Executions.

The Executions page consists of two panels:

  • Executions History - Lists the details of all recent executions that have occurred in the selected environment, for every type of executable data stage. Executions are listed in a grid, with the following columns:
    Column Description
    Stage Name The name of the data stage that was executed.
    Stage Type The type of the data stage that was executed.
    Start Time The time that the execution started.
    End Time The time that the execution ended.
    Execution Time The duration of the execution.
    Status Whether the execution succeeded or failed.
    Work Id The Work Id of the execution. The Work Id can be used, for example, to control how an analysis loads its data. For more information, see Using Work ID Parameters.
    Process Id The Id of the process model run that triggered the execution. If the execution was not executed as part of a process model run, this column contains no value.
    Execution Engine Id The Id of the execution engine.
    Ref Start Time Refers to the time of the previous execution of the data stage. For example, if an analysis is configured to load new data since the last execution, Ref Start Time will contain a timestamp of the last time data was loaded for the analysis.
    Ref End Time Similar to Ref Start Time, this can be used by a data stage to determine the new data to be loaded. For example, when an analysis runs, its start time is used as the value of Ref End Time and will be used as the Ref Start Time the next time the analysis is run.
    Is Rebuild Displays whether the execution was a rebuild. Possible values are 'yes' to indicate a rebuild, and 'no'. It is useful to know whether an execution was a rebuild or not, because a rebuild overrides the data load configuration of a data stage, and loads all data before executing.
    Trigger Params Displays any parameters that were passed to the executed stage before execution. For example, in a process model, system or user defined parameters can be passed between nodes in the process model.
    Result Code The result code of the execution. For more information about result codes, see Execution result codes.
    Result Details Provides additional information or messages about the execution. When an execution fails with result code 1, details are provided in this column. If the execution relates to a data view that no longer exists, this information can be displayed in this field.
    Started By Displays a user ID if an execution was started manually, including actions started via the API. This makes it easier for users to collaborate on resolving issues with the operation of the system.

    You can perform the following actions:

    • Terminate - Stops a run or rebuild mid-process.
    • Rollback - Reverts a data stage to the state it was in just after its last run or rebuild.
    • Rerun - Allows you to perform a run from within the Executions History.
    • Refresh - Updates the list of executions.
    • Filter - If you have a long list of executions, you can filter to search for a specific one.
    • Filter By Process Id - If you have selected a process model, you can filter by the process ID of the selected process model to see a list of data stages that were executed during a specific run of that process model.
    • Download Log - Allows you to download log information for a selected execution. You cannot download log information for process models, data store load triggers, or case store execute triggers.

     

  • Execution Details - Displays further details of the currently selected execution. For example, for an analysis execution, the analysis nodes are displayed along with the number of output records for each node in the analysis, and whether each node succeeded or failed.
Tip: You can also create Process Models to manage complex dependencies.

Execution result codes

Executions complete with a result code that represents the status of the execution. You can use result codes in process model expressions, to create the model's logic. When an execution completes it returns one of the following result codes:

Result code Execution status Description
0

Succeeded

The data stage has executed without error.
1

Failed

Something has caused the execution to fail. More details should be available in the Result Detail field.

9

Lease Expired

The Data360 DQ+ execution engine features an Expired Lease Job, which checks for inactivity due to random error from machine or process crashes.

If an execution has crashed, it will be marked with a Status of Lease Expired and a Result Code of 9.

8

Terminated

Applies to a process model that was running when one of its constituents crashed.

If the Expired Lease Job finds a crashed data stage execution and that data stage is part of a process model, the process model will be terminated.