DocsHow it WorksView ResultsView Results This page walks through where to find pipeline runs in the dashboard and what each part of a run’s page shows. See How It Works for the underlying model. Find a Run Open the Execution section of the dashboard. It lists every run for the current organization, most recent first, with columns for status, mode, entrypoint, tags, parameters, resources, instance, start time, and duration. Click a run to expand its row and see a quick summary inline, or open it to reach the full run page. If the run belongs to a group (for example, several runs triggered together), a See group button on the run page takes you to the group view, listing every run in the batch. Read a Run’s Page Header The top of the run page shows the run’s status, its mode (direct or distribution), the entrypoint that was launched, any tags and parameters it was launched with, and its total resource usage and duration. Pipeline Graph Below the header, the pipeline itself is rendered as a graph of treatments and connections, reconstructed from the program that was actually executed. If the run produced debug events, a timeline appears alongside the graph, scrubbing through it highlights the treatments and connections active at that point in time. Resources A Services section lists every part of the run, the engine itself, each container, each service container, and any mounted volumes, with its image (for containers) and its CPU, memory, and storage. A Required Resources section breaks total memory, CPU, and storage down per entity, alongside a timeline of when the run was requested, started, and finished. Logs The Logs panel streams the run’s logs in near real time: it polls for new chunks every few seconds while the run is ongoing, and stops once the run has finished. Logs can be downloaded as a single file at any time, including while the run is still in progress. Debug Data If debug reporting was enabled for the run, a Debug panel is available below the logs. It’s hidden by default, click to reveal a raw, explorable view of the debug events captured during execution, and it can be downloaded the same way as logs. Going Further Connect a Cloud, how the instance running a given step was chosen. How It Works, what’s captured today versus what’s on the roadmap. Connect a CloudProgramming Language