Viewing Task Runs

When you run a task in an application, a run entry is created in the application.

For a data loader task that is configured with the multiple entities load type, a parent run entry is created and a child run entry is created for each entity-loading operation. Similarly, for a pipeline task, individual run entries are created for the tasks within the pipeline's main run entry.

Run entries are also created for tasks that run automatically based on conditions set in task schedules and associated schedules.

All the task runs that have been created for all published tasks in an application are found in the Runs section of the application details page.

All the task runs for a specific task in an application are found in the Runs section of the task details page.

The run entry details in either Runs section are the same.

  • The following procedure describes how to list all runs in an application.

    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 runs that you want to view.
    4. On the application details page, click Runs.

      The Runs page shows the following run entry details:

      • Name: Name of the run created. To see run details, click the name. If applicable, expand the main run entry to see the individual child run entries.
      • Status: The status of the run.
        • Not started: Appears when a task run is initiated manually or by a task schedule, but is not yet submitted to the execution engine.
        • Queued: Indicates that the task run is waiting for execution. The status transitions to Running once resources are available.
        • Running: Indicates that the task run is in progress.
        • Success: Appears when the task run is completed successfully, with no errors.

          For a pipeline task run, a status of Success depends on the rule that is set on the end operator. See Start Operator and End Operator.

        • Error: Indicates that the task run encountered one or more errors and didn't complete successfully.
        • Terminating: Indicates that the task run is in the process of being stopped (terminated).
        • Terminated: Indicates that the task run was stopped (terminated).
      • Type: The type of task that was run. The type column is not available on the task details page.
      • Data read and Rows written: The amount of data processed, and the number of rows inserted or updated.
      • Started and Ended: The start time and end time of the task run.
      • Duration: The duration of the task run.
      • Initiated by: The initiator of the task run.

      A pipeline task run includes task runs for all the tasks in the pipeline orchestration. If a child task run fails, subsequent tasks in the sequence do not run.

      When viewing the task run details for a pipeline task, expand the main run entry to see the task run details for individual tasks in the pipeline sequence.

      For a pipeline run, the actual pipeline run start time and the length of a run can be longer than expected. Running a pipeline includes pre-processing, acceptance, and validation steps before the execution engine starts the actual pipeline run. Each step might take one to five minutes. In between those steps are reconciliation processes that also might take a minute or more.

      If one of the task runs in a pipeline fails, the pipeline does not reach its final state immediately. Suppose that a pipeline has N tasks. If the Mth task run fails (where 1 <= M < N), the pipeline reaches its final state in (N - M) x 60 seconds.

      The Actions menu of a run entry has the following options:

      • Copy task run key: Copies the key of the task run to the clipboard. You can use the key with APIs.
      • View logs: Displays any logs in the Log message panel. Logs are only available for task runs that don't complete successfully.
      • Rerun: Runs the task using another run identifier.

        For a pipeline task, you can rerun the main task only. You can't rerun individual child tasks within the pipeline. Similarly, for a data loader task that loads data into multiple entities by using a run entry for each entity-loading operation, you can rerun the parent task only.

      • Terminate: Stops a task run that is in progress.
    5. To find a particular task run in the Runs list, enter a partial name or the full name of a run in the Filter by name field and press Enter.
    For information about the details in a task run, see Viewing a Task Run's Details.
  • Use the oci data-integration task-run list command and required parameters to retrieve the task runs in an application in Data Integration:

    oci data-integration task-run list [OPTIONS]

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

  • Run the ListTaskRuns operation to retrieve the task runs in an application in Data Integration.