Creation
- Open Configs → New Flow → Pool of transit nod.
- Give me a name and a description.
- On the Holst tab, add transit nodes and assign physical servers.
- Set up connections, transports and exits. Settings Ask the pool policy.
- Save the pool, then select it in the transit block of regular Flow.
Beginning, transitions and continuation
Inside the pool are Gateway (beginning of the site), Internet and Continue flow. The new transit node receives initial connections from Gateway to the node and from the node to the continuation. By connecting the nodes to the chain, check the arrows: the location of the cards does not in itself specify the order of transitions. Here, A and B are alternatives to the first junction. The node selected sends traffic to the next transit of the external Flow. If inside the pool the branch ends in Internet, it ends there and does not use the external extension. If the pool uses Continue Flow, the next section must be specified outside the Pool Node, and the missing or unused continuation is diagnosed at compilation.Conditions and limitations
- Parallel transits form balanced alternatives; different sequential transitions are not combined into a single list of servers.
- Cycles, dead ends, ambiguous outputs and detached author nodes are not allowed.
- Routing conditions within the pool are maintained.
- Unconditional internal continuation supports conditional external routes.
- If the inner continuation itself is conditional, exactly one unconditional next block is allowed outside, and the simultaneous conditions on both sides of this boundary should be transferred to one side.
- The WARP after the pool must be ready on all physical nodes that can complete this pool.
Changes and applications
Saving the pool updates the directory. Already running Flows continue to use the fixed snapshot until the next explicit application. The Flow Studio review shows which Flows are waiting to check for pool changes. Before use, examine the effect of the new composition and graph, including nodes excluded throughenabled or drained. Re-assemble the plan if the pool changes after viewing it. In case of an audit conflict, download current data so that you do not overwrite the editing of another operator.
Old pools without their own graph retain the same behavior. If the editor offers them an initial canvas, check the transports and connections before using Flow.
