For the complete documentation index, see llms.txt. This page is also available as Markdown.

Run

A single execution of a Pipe.

A Run is one execution of the workflow associated with a Pipe.

Every time Pipekit submits the Pipe's workflow to a Cluster, it creates a Run. Submissions can come from the CLI, the UI, a Git event, a cron schedule, or an external trigger. The Run captures status, start and end times, parameters, pod logs, and the workflow node graph. Pipekit retains Runs indefinitely; old Runs are never garbage-collected.

You can stop, terminate, retry, or resubmit any Run from the Pipekit UI or CLI. Workflow lifecycle commands map directly to Argo Workflows operations on the underlying Workflow resource. Pipekit is a thin layer over Argo's existing semantics.

For task-oriented documentation, see Using Pipekit > Runs.

Last updated