Run pipeline executions

​

Executions dashboard

The executions dashboard helps you manage the status of your executions, including running, aborted, failed, completed, and more.

On the Executions tab, you can see the list of executions, including the following information:

• Execution numbers and status of each execution
• Person (or triggered reason) who triggered the execution
• Duration
• Timeline (Started, Finished) that shows the time when you run execution and finish.
• Action buttons
  • Reproduce: Trigger a pipeline execution with the same variables.
  • Abort: Stop the running execution.

​

Filter

You can apply the filter by status or assignee to easily find the execution you want.

​

How to run a pipeline execution

Once you have published a pipeline revision, you can run execution using the button on the revisions tab. The new execution will always be created with the latest revision of the pipeline.

You can also run executions in the Executions tab. Refer to the demo below and explore its functions.

​

Execution details

When you click on the execution from the execution list table, you can navigate to the execution detail page.

Execution detail page includes the following information:

• Metadata: Metadata of the execution including ID, status, duration, and triggered time.
• Pipeline variables: Variables injected during a pipeline execution.
• Graph: Visualized graph view of the execution.
• Step details: Detailed list of steps ran during the execution.

You can also click each step to see the detailed information of the step, including the logs or data of the output volumes.

​

Debug mode

Debugging complicated workflow is always challenging. To help you debug a pipeline execution, you can enable the debug mode when you trigger the pipeline execution.

When the debug mode is enabled, the pipeline execution will be paused instead of get terminated when one of the Run step has failed. This allows you to access the container through SSH to troubleshoot the issue and resume the execution.

When the executions are paused for debugging, you can see idle status on the execution list and actions enabled on the detail page. You can also see the logs that the container opened SSH access for debugging.

Actions available on the detail page:

• Resume: Mark the step as successful and continue the execution.
• Abort: Stop the running execution.
• Debug: Connect to the container through SSH.