Manage executions - Data360_DQ+ - Latest

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.