Graph info: a graph's profile pages
Everything about one graph outside the canvas — authors, runs, schedule, source, revisions, nodes, linked graphs, configuration, and checks.
Each graph has a set of Graph info pages beside the editor. Open them with the ⓘ (Graph information) button on a row in a graph list, or from the links in the editor's readiness strip and Validate popup. The rail on the left switches pages, and Open in editor → returns to the canvas.
The pages
- Overview
- Name, id, counts (authors, levels, nodes), created/updated times, recent runs, and quick links to every other page.
- Authors
- Owners, who created it, and who last updated it.
- Runs
- Who has run the graph and how often, plus a timestamped list linking to each run.
- Schedule
- Recurring and one-off run rules and a month calendar — see Running a bot on a schedule.
- Source
- Links to the graph's catalog source and its git history.
- Revisions
- Saved revision snapshots (label, kind, id, times). Read-only here — in the editor, History → Save snapshot creates one and Restore revision… goes back to one.
- Nodes
- Every node, one table per level — often faster than hunting on the canvas.
- Linked graphs
- This graph and every graph it calls through sub-graph nodes. Graphs draws each one as a box, with arrows from caller to callee labelled with the call sites and the values passed in and out. All states shows every state inside each graph; double-click a sub-graph container to open its level, and use the breadcrumb on the frame to go back up.
- Configuration
- Which nodes still need setup, and what is missing. Fix → and Focus → open the editor on that node.
- Validation, Tests, Checks
- Results from the last Validate and Test runs — see Checks, validation, and pipeline history.
- More
- Filtered audit and runs lists for this graph, a document summary, and recent audit events.
Related
- Checks, validation, and pipeline historyGraph editorWhere the results of Validate, Test, and Simulate are kept, stage by stage, and how to jump from a problem to the node.
- Running a bot on a scheduleRunning & debuggingGive a graph a calendar so it runs on its own — once at a set time, daily, every other day, weekly, or any combination.
- Read run history and tracesRunning & debuggingThe runs list, per-run traces and logs, and the run pages hanging off a graph.
- Find things in a large graphGraph editorIn-context find, quick open, and the command menu for navigating graphs too big to scan.
More in Graph editor · Search all help