/help/run-a-graph

Loading…

Help center

All topics & search Table of contents Getting startedWhat GraphVM is, the console and dashboard, search, and building your first graph.Graph editorThe editor views, drawing and wiring nodes, the inspector, graph info pages, and checks.Nodes & catalogBrowsing node types, scopes, the connection taxonomy, and reusable nodes.Running & debuggingRun configuration, breakpoints, run pages, logs and output, and controlling live runs.AI generationDescribing a workflow in prose and refining the graph the builder produces.Credentials & modelsAPI keys for integrations, secret references, and LLM access and budgets.Workspace & adminWorkspace defaults, users and teams, billing, security, your profile, and the audit log.ReferenceKeyboard shortcuts, glossary, and pointers to the API documentation.

Reachable from Help → Help center, or press ⌘K and search.

Help center/Running & debugging

Run a graph

Supply the input, clear validation, start the run, and find it afterwards.

In the app

Run history

Open the graph in the editor and switch the right rail to Run.
Provide the graph input as JSON if the graph expects one — this is what the Start boundary receives.
Check the validation summary in the panel footer; Run and Debug are disabled while errors remain.
Press Run for a normal execution, or Debug to run under the debugger with breakpoints honoured.
Follow the execution in the rail, then open the run from /runs for its full trace.

NotePer-node values (and secrets) do not belong in the input payload — they come from the node's saved config plus the active run preset in Run cfg.

Related

Run configuration and presetsRunning & debuggingPer-node arguments for a run, saved as named presets you can duplicate, export, and seed from the last run.
Debug with breakpointsRunning & debuggingPause execution at a node, step, inspect agent memory, and manage breakpoints across graphs.
Read run history and tracesRunning & debuggingThe runs list, per-run traces and logs, and the run pages hanging off a graph.
Live runs, suspension, and resumingRunning & debuggingWhere a currently-executing run shows up, why its history page can 404, and how suspended runs continue.

More in Running & debugging · Search all help