DocsBook a demo

Platform

Platform overviewArchitectureWorkflow orchestrationGitOps configurationGovernance and AAAAI and MCPKnowledge and contextRuntime and executionEvidence and monitoring

Use cases

All use casesProduction incidentRelease preparationHotfix to productionSecurity scan triage
Why NopsAIIntegrationsSecurity

Resources

All resourcesAI agent governanceMCP governanceMCP securitySelf-hosted platforms
PricingGitHub

Company

How a run worksAboutContactBook a demo

Pipeline runs

Reading a run: the execution graph, step and task detail, outputs, and what each status means.

How-toOperatorAutomation author

Key points

  • Run detail separates Graph and Outputs tabs. Selecting a multi-task step reveals its task DAG below the step overview.
  • A run finishes success, failure, warning, timed_out, or canceled.
  • warning means work failed but was ignored: the failing task stays auditable as failure (ignored).
  • timed_out is what an expired approval timeout or run timeout produces.
  • Run list surfaces expose only aggregate final_output_status; generated content stays on authorized detail paths.
  • Pipeline detail is organized as Flow, Definition, Trigger rules, Runs, Health, and Dependencies tabs.

Before you start

Access
Read access to runs in the team that owns the pipelinecurl -s -H "Authorization: Bearer $NOPSAI_TOKEN" "$NOPSAI_URL/v1/auth/me" | jq .capabilities
A run to read
A run ID, from the run list or from the pipeline detail Runs tab

Steps

  1. 01

    Start from the run list

    Pipeline Runs and GET /v1/runs return the same records. Filter by team with teamId, or by branch with branch.

    List recent runsbash
    curl -s -H "Authorization: Bearer $NOPSAI_TOKEN" "$NOPSAI_URL/v1/runs?limit=20" | jq '.[] | {run_id, pipeline_name, status}'
    Replace before running
    • $NOPSAI_URL is the API address, http://localhost:8080 on a local install.
    Expected result
    • Runs newest first, each with a status of success, failure, warning, timed_out, or canceled.
  2. 02

    Open the run and read the graph

    Run detail carries the execution graph and per-step state. Selecting a multi-task step reveals its task graph below the step overview.

    Fetch run detailbash
    curl -s -H "Authorization: Bearer $NOPSAI_TOKEN" "$NOPSAI_URL/v1/runs/$RUN_ID" | jq
    Verify
    • The failing step is identifiable by status before you open any logs.
  3. 03

    Separate ignored failures from real ones

    A warning run contains at least one failure that was ignored. Find it before concluding the run was fine.

    Expected result
    • An ignored failure is recorded as failure (ignored) and stays auditable.
  4. 04

    Act on the run

    Re-running starts a fresh run from the same definition; cancelling stops one in flight.

    Rerun or cancelbash
    curl -sX POST -H "Authorization: Bearer $NOPSAI_TOKEN" "$NOPSAI_URL/v1/runs/$RUN_ID/rerun" | jq -r .runId
curl -sX POST -H "Authorization: Bearer $NOPSAI_TOKEN" "$NOPSAI_URL/v1/runs/$RUN_ID/cancel" | jq
    Verify
    • The rerun appears in history as its own record; the cancelled run finishes canceled.

How it works

The expanded graph dialog supports scroll-zoom traversal of larger graphs, centers bounds when a run opens or Fit is pressed, and keeps the task reveal during zoom and pan. Unmodified wheel input still scrolls the page outside expanded graph mode.

The Health tab owns the full pipeline analysis result and the AI Evaluation surface. The Analyse Pipeline header action switches there rather than opening a separate modal.

Copy actions across pipeline YAML, step YAML, trigger YAML, knowledge content, credential references, run definition YAML, and run graph links all use the shared clipboard helper, so the selection-copy fallback works when the browser Clipboard API is unavailable.

Implementation evidence

  • services/nopsai/routes.go

    Run lifecycle, approval, and output routes.

  • doc/runtime-flows.md

    Cancellation, rerun, and child pipeline flows.