Viewing a Task Run's Details

• Console
• CLI
• API

• 1. On the workspace home page, click Applications.
  2. On the Applications page, select the compartment that contains the application.
  3. In the applications list, click the name of the application that has the task run that you want to view.
  4. On the application details page, click Runs.
  5. In the Name column of the Runs list, click a task run name. For a pipeline task, click the name for the main run entry.

     The task run details page opens and displays general information and an Overview section that shows the following information:

     • Basic metrics such as task type, run status, run duration, and the amount of data processed
     • A run duration bar chart view of up to five previous runs of the task. If previous runs are not available for this task, the following message is displayed instead: No data available to display
     • The parameters and configured values that are used in the current run
  6. For a pipeline task run, click the Pipeline graph tab to see details of tasks and activities in the pipeline from start to finish in a graphical form. The successful and failed paths, and the run status of a task or activity node, are indicated on the graph. Where applicable, the incoming link condition of a node is also shown.

     • On the pipeline graph, you can perform the following actions:

       • Move the entire pipeline to change the view.
       • Zoom in or zoom out to change the focus.
       • View the pipeline parameters and configured values that are used in the current run.
       • Select a node in the pipeline to see more details, including parameters and configured values.
       • Refresh the graph, if the pipeline task run is yet to complete.

     • If a node is Failed, any downstream node with the All success condition is skipped. However, that "skipped" node is considered to be a failed node even though the status indicator is Skipped. Thus, nodes that are skipped because of a predecessor node error are counted as failed when evaluating execution rules downstream.

     • It can appear that a pipeline run is still processing nodes in certain paths even though there are already individual nodes in the path that are marked Skipped, Ignored, or Failed. For example:

       • An upstream node failed, and there are downstream nodes that are set with the All success condition.
       • The False path from a decision operator includes several tasks, the first of which is skipped. However, each task following the first task is skipped only when it's picked up for execution after the normal delay between task runs in a pipeline.
  7. To see error messages and copy OPC request identifiers for troubleshooting, click View log.

     Data Integration displays the Log message panel.

     In a Data Integration service task run, logs are only available for task runs that don't complete successfully.

     For a task that's configured to run in the OCI Data Flow service, click the Data Flow application run page link to navigate to the OCI Data Flow service page to view the logs. Log files include standard data and diagnostics output logs for the OCI Data Flow application, Spark drivers, and Spark executors.

• Use the oci data-integration task-run get command and required parameters to retrieve a task run in an application in Data Integration:

  Copy

  oci data-integration task-run get [OPTIONS]

  For a complete list of flags and variable options for CLI commands, see the Command Line Reference.

• Run the GetTaskRun operation to retrieve a task run in an application in Data Integration.