Validate a graph and fix problems
Where validation errors come from, where they surface, and why Run can be disabled.
Validation runs at four points, each catching something different:
- Field level (client)
- Required fields and secret-reference format, shown inline on each input.
- Graph input (client)
- Invalid input JSON blocks Run and Debug.
- Server, debounced
- While the Run panel is open the console posts the graph to the agent's validate endpoint with the current level, input, and node arguments; the summary lands in the panel footer.
- Server, on run
- The same merge plus per-node payload checks before execution starts.
Structural problems also appear in the Code view's Problems subtab, and a graph's Checks page under Graph info collects its check results.
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.
- Run a graphRunning & debuggingSupply the input, clear validation, start the run, and find it afterwards.
- The editor viewsGraph editorAI Generation, Code, Drawing, and Schematic are four views of one graph's definition; Run / Debug is the view of its execution.
More in Graph editor · Search all help