> ## Documentation Index
> Fetch the complete documentation index at: https://docs.axottle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Transit pools

> Reusable routes with its own canvas, several transitions and a continuation of Flow.

A transit pool is a reusable section of the path. It contains its own graph, participants and balancing policy. Regular Flow connects it via **Pool Node** in the transit unit settings.

## Creation

1. Open **Configs → New Flow → Pool of transit nod**.
2. Give me a name and a description.
3. On the **Holst** tab, add transit nodes and assign physical servers.
4. Set up connections, transports and exits. **Settings** Ask the pool policy.
5. Save the pool, then select it in the transit block of regular Flow.

The pool has two tabs: **Holst** and **Settings**. Input nodes, CDN and nested Pool Node inside the pool are prohibited.

## 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.

```mermaid theme={null}
flowchart LR
    E[Входная нода Flow] --> G
    subgraph Pool[Транзитный пул]
      G[Gateway] --> A[Транзит A]
      G --> B[Транзит B]
      A --> C[Продолжить flow]
      B --> C
    end
    C --> N[Следующий транзит Flow]
    N --> I[Internet]
```

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 through `enabled` 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.

## Managed change of several Flows

To re-link the pool, examine the pre-impact and verification queue of those affected by Flow\.Certification relates to a specific composition, graph and audits: the change after viewing requires a new plan.

The application operation is stored on the server. Leaving the page does not mean canceling. After an interruption or partial error, open the result and check each Flow; the available continuation, acceptance, and rollback actions depend on the status of the operation.

Do not run a parallel manual fix of the general runtime until the previous operation is completed or dismantled.The rollback of the operation returns fixed snapshots of affected Flows and pools; conventional directory editing does not replace this rollback.

## Verification

Check the regular Flow plan, each pool transition, continuation and behavior when candidates are unavailable. The saved pool does not mean that the new scheme is applied and tested on the nodes. The strategies and rejection policy are described in the [balance](https://docs.axottle.com/en/connection-units/balancing.md).

## Rollback

Prior to application, correct the pool directory: working pictures remain the same. After application, restore affected Flow through the [version or managed application report](https://docs.axottle.com/en/connection-units/lifecycle.md#откат). Returning the name or pool composition in the directory does not roll back deployed configs by itself.

Check the availability of features in the installed version in the panel; this reconciliation does not confirm the deployment on the servers.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.