# View and manage pipelines > View and manage pipelines - Open a pipeline in Registry to inspect the workflow DAG, configuration, > and run history. This Markdown file sits beside the HTML page at the same path (with a `.md` suffix). It summarizes the topic and lists links for tools and LLM context. Companion generated at `2026-09-30T19:40:40.936173+00:00` (UTC). ## Primary page - [View and manage pipelines](https://docs.datarobot.com/en/docs/workbench/nxt-registry/pipelines/view-manage-pipelines.html.md): Full documentation for this topic (Markdown sidecar). ## Sections on this page - [Draft and Locked pipelines](https://docs.datarobot.com/en/docs/workbench/nxt-registry/pipelines/view-manage-pipelines.html.md#draft-and-locked-pipelines): In-page section heading. - [Workflow view](https://docs.datarobot.com/en/docs/workbench/nxt-registry/pipelines/view-manage-pipelines.html.md#workflow-view): In-page section heading. - [Task list](https://docs.datarobot.com/en/docs/workbench/nxt-registry/pipelines/view-manage-pipelines.html.md#task-list): In-page section heading. - [Details](https://docs.datarobot.com/en/docs/workbench/nxt-registry/pipelines/view-manage-pipelines.html.md#details): In-page section heading. - [Next steps](https://docs.datarobot.com/en/docs/workbench/nxt-registry/pipelines/view-manage-pipelines.html.md#next-steps): In-page section heading. ## Related documentation - [NextGen UI documentation](https://docs.datarobot.com/en/docs/workbench/index.html.md): Linked from this page. - [Registry](https://docs.datarobot.com/en/docs/workbench/nxt-registry/index.html.md): Linked from this page. - [Pipelines](https://docs.datarobot.com/en/docs/workbench/nxt-registry/pipelines/index.html.md): Linked from this page. - [Runs](https://docs.datarobot.com/en/docs/workbench/nxt-registry/pipelines/run-schedule-pipelines.html.md#view-run-history-and-logs): Linked from this page. - [Manage pipeline images](https://docs.datarobot.com/en/docs/workbench/nxt-registry/pipelines/pipeline-images.html.md): Linked from this page. - [Draft and locked pipelines](https://docs.datarobot.com/en/docs/workbench/nxt-registry/pipelines/pipeline-overview.html.md#draft-and-locked-pipelines): Linked from this page. - [Add a pipeline](https://docs.datarobot.com/en/docs/workbench/nxt-registry/pipelines/add-pipeline.html.md): Linked from this page. ## Documentation content After adding a pipeline, click the Pipelines tile. Each listing shows the pipeline name, any description, and Draft or Locked status. Select a pipeline to inspect its graph, configuration, and run history. The page opens to Workflow view for the selected pipeline—one of three available tabs: | Tab | Description | | --- | --- | | Workflow view | An interactive directed acyclic graph (DAG) for inspecting task-level telemetry and output. | | Details | Pipeline identity, tasks, current input, and the bound image. | | Runs | A chronological log of previous runs. | The Images tab lists container images. For more information, see [Manage pipeline images](https://docs.datarobot.com/en/docs/workbench/nxt-registry/pipelines/pipeline-images.html.md). ## Draft and Locked pipelines A pipeline has two states. - Draft . Logic, inputs, and image can be modified; use this state while iterating. - Locked . Logic and environment are immutable; recurring schedules can target only Locked pipelines. For the concept definitions, see [Draft and locked pipelines](https://docs.datarobot.com/en/docs/workbench/nxt-registry/pipelines/pipeline-overview.html.md#draft-and-locked-pipelines). To lock a pipeline and attach a schedule, see [Lock and schedule](https://docs.datarobot.com/en/docs/workbench/nxt-registry/pipelines/run-schedule-pipelines.html.md#lock-and-schedule). ## Workflow view Workflow view renders the task-call graph as a DAG. Each node is a `@dr.task` function. Independent branches run in parallel; downstream tasks wait for their inputs. For the selected run, the view shows: - The run timestamp, ID, and status (for example, Run completed ). - Each task node with its status and run time. - A task list on the right. Use the zoom controls to inspect the graph. ### Task list From the task list on the right, click and expand a task. The expanded task has three tabs for additional information. **Details:** The Details tab shows when and how this task ran, the resource bundle it used, and the function source. Field Description Triggered by How the run started (for example, On-demand). Started When the task started. Run time How long the task took. Resource bundle Compute size for the task (for example, S , 1 CPU / 512MB RAM). Code The @dr.task function source for this node. **Return value:** Return value is what that `@dr.task` function returned for the selected run—the object that DataRobot passes to downstream tasks as arguments. Nothing is shared through files or memory except this value. The tab provides a JSON preview of the result (in the example, `prepare_data` shows `[[140, 1], [130, 1], …]`). Click Download raw value for the full stored object (including objects that do not preview cleanly, such as a fitted scikit-learn model). [https://docs.datarobot.com/en/docs/images/pipeline-return-value.png](https://docs.datarobot.com/en/docs/images/pipeline-return-value.png) **Logs:** The Logs tab shows console output from the task for the selected run. Click View logs on a task in the list to open this tab. The tab provides: stdout (standard output): Text the task writes with print() . stderr (standard error): Warnings, exceptions, and Python tracebacks. When a task fails, the traceback is usually here. Refresh, copy, or download from the icons on the pane. ## Details The Details tab summarizes pipeline configuration: identity and timestamps, the task list, the current input payload, and the bound image. The following table describes the fields on Details. | Field | Description | | --- | --- | | Pipeline ID | Unique identifier for the pipeline. Click the copy icon to copy the ID. | | Latest version | Locked version of the pipeline. None yet (draft) appears when the pipeline has not been locked. | | Python version | Python runtime for the pipeline (for example, 3.12). | | Created | When the pipeline was created. | | Modified | When the pipeline was last changed. | | Tasks | Each @dr.task in the DAG and the resource bundle assigned to that task (for example, S, 1 CPU / 512MB RAM). | | Current input | YAML payload used by the most recent run. Each run can override this payload. | | Current execution image | Image bound to the pipeline: Name, Version, Build status, image Python version (or Platform default), and the packages list. | ## Next steps After reviewing a pipeline, run it, configure a schedule, or return to the list to add another pipeline. - Run and schedule pipelines : Run the pipeline, lock it, and review run history and logs. - Add a pipeline : Create another pipeline from Python source, inputs, and an image. - Manage pipeline images : Create or rebuild the container image used at run time.