03/Flow Routing
The Flow Strategy
The strategy that turns a model group into an admin-drawn routing graph.
Flow turns a group's strategy into a graph: ENTRY → ROUTER(s) → MEMBER(s). Every request enters at ENTRY, passes through routers, and reaches a member (a real model). Routers are the decision-making nodes.
Entry
routerRoutercontent / rule / score…
Member Amodel + node
Member Bmodel + node
#Edge types
- route
- Leaves an entry or router; the "forward" direction of the graph. Followed based on the router's decision.
- status
- Leaves a member; defines a jump to another member/router when an upstream HTTP error (429, 5xx…) occurs (failover).
- self-loop
- A member's status edge back to itself: retries the same member a set number of times (self-retry).
#default_target
If no rule matches at the end of the chain or all targets become unusable, the optional default_target is tried once. If that also fails, the last upstream error is returned to the client — a request is never turned into an internal 500.
The flow graph is drawn visually in the panel via "Model Groups → a group → Flow". This documentation explains the behavior behind that graph.