AGENTFLOW · GRAPH VALIDATION
Flowise-style Agentflow: validate a disconnected tool node
Edit a four-node agent graph, validate reachability before running it, and see what the agent answers when its tool is disconnected.
Event trace
Computed data
Final metrics
Graph model inspired by visual agent builders such as Flowise; it is not Flowise and reads no exported flow JSON. The agent always wants a price, calls PriceTool when an edge allows it, and replies once it has a result or no tool edge remains. The tool returns a fixed fictional price.
A graph can look complete and still be wrong
The flow has four nodes: Start, Agent, PriceTool and Reply. The user asks for the price of SKU-42, so the agent should call PriceTool and reply with its result. Edges are typed as From -> To, one per line. In the opening graph PriceTool has an edge back to Agent but nothing leads into it. Validation finds that PriceTool is not reachable from Start, and with Validate before running enabled the run is refused before it can answer.
What happens without validation
Clear Validate before running. The agent visits Start, Agent and Reply. With no edge to PriceTool it never calls the tool and replies that SKU-42 probably costs around 20 EUR: an ungrounded answer that looks plausible. Load the connected tool loop: validation passes, the agent calls PriceTool once and replies that SKU-42 costs 19.50 EUR, with the source stated. The orphan example, with no tool edges at all, fails exactly like the disconnected one.
Iteration limits and cycles
In the connected graph the agent needs two iterations: one to call the tool and one to reply. Set Maximum agent iterations to 1 and the run stops at the iteration limit after a single tool call, with no reply. Load the example with no path to Reply: validation reports that Reply is unreachable. Without validation the agent and tool call each other until the limit; with three iterations PriceTool is called three times, and with six it is called six times, still without a reply.
Edit the edges yourself
The edge editor is live. Load the misspelled example: the line Agent -> PriceTol names an unknown node and is ignored, so validation reports two errors, the unknown node and the unreachable tool. Fix the spelling and the graph becomes valid. Add a line that is not in From -> To form and it is reported by line number. The computed data table lists the edges actually parsed. Play, Next event, Restart, Speed and Inspection time follow parsing, validation and each step of the run.
What this is not
The graph is inspired by visual builders such as Flowise Agentflow but does not read Flowise exports or implement its node types, conditions or memory. The agent policy is fixed: call the tool when an edge allows and no result exists yet, otherwise reply. The point is general: validate reachability of every required node before deployment, because an unreachable tool silently becomes an answer without evidence.