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

# Flow Studio: Review

> How Flow Studio connects inputs, routes, transit pools, and working configurations.

**Flow** is the configuration of the traffic path that you collect on canvas, check and apply to the infrastructure. Open **Infrastructure → Configuration**: the workspace of this section is called **Flow Studio**.

This entity used to be called **Connection Unit**. The page address `/new/connection-units` and API `/api/v1/connection-units` remain unchanged.

## What's in Flow Studio

\| Section | What you need | for
\|---|---|
\| **Review** | Status of applied Flow, problem queue, unused pool changes and risk analytics. |
\| **Configures** | Flow list, search and filters for health, drafts and problems. |
\| **Transit pools** | Reused transit routes with own canvas and balancing policy. |
\| **PARK HAProxy** | [Servers named connections and pools ](https://docs.axottle.com/en/connection-units/haproxy-park.md), which are used through associated Flow. |
\| **Objectives of Reality** | [Search and verification](https://docs.axottle.com/en/connection-units/reality-targets.md) The candidate found doesn't mean a suitable target. |

[Telegram-proxy](https://docs.axottle.com/en/connection-units/telegram-proxies.md) is a separate MTProto park and WEB in the same space. Each record unfolds on a single node and gives out its own link; this script does not use a regular Flow canvas.

## What makes the New Flow button?

If the route is already running on Remnawave, use it.
[Import of the existing](https://docs.axottle.com/en/connection-units/remnawave-import.md) scheme.
It creates an observable image after approval. Separate transformation.
prepares a managed draft, and application to servers remains a clear action.

First, select the appointment:

* **Normal Flow** is a full route with an input node, client settings and its own applied versions.
* The **transit nod** is a reusable portion of the route that is stored in the directory and included in the regular Flow via Pool Node. The pool itself does not publish the client connection.

In a conventional Flow, the wizard offers a single (`standalone`) or balanced (`balanced`) mode. The value of `mixed` remains a compatible technical value for existing configurations, but there is no separate card of this mode in the wizard.

On a beginner's tour, type selection is skipped: a short master of the regular Flow immediately opens. Once created, training continues on his canvas; creating a transit pool is not included in the tour.

## What the route consists of

```mermaid theme={null}
flowchart LR
    G[Gateway] --> E[Входная нода]
    E --> T[Транзитная нода или Pool Node]
    T --> I[Internet]
```

The minimum Flow is `Gateway → Входная нода → Internet`. You can add a CDN before entering, a transit chain, WARP, an external proxy, an external VLESS transit, and a traffic lock.

Gateway marks the beginning of a circuit; it is not an automatically created separate physical server; input and managed transit blocks are tied to real nodes; masking and SelfSteal are configured at the respective nodes and transports.

## Three independent states

| What is shown by | How to read |
| - | - |
| **drafter** | Something you're editing and haven't applied yet. |
| **Applicable version of** | Configuration shot sent to infrastructure. |
| **Health** | The result of checks of the running route taking into account their time and version. |

Flow can run on the same version at the same time and have a modified draft. Successful use does not in itself prove the availability of a client route. Missing or outdated checks are not considered validation.

## What does the customer get?

The display name, customer description (up to 30 characters) and user group are set in the normal Flow settings. The route settings take effect after application; the description, user group and data collection of inaccessible sites are stored separately and are effective immediately.

To provide a configuration to the user, set up [subscription page](https://docs.axottle.com/en/subscription-page/overview.md) and check the connection by the client.

## Next steps

> [card] [Designer](https://docs.axottle.com/en/connection-units/constructor.md)
>
> Blocks, Communications and the First Flow.

> [card] [Application and versions](https://docs.axottle.com/en/connection-units/lifecycle.md)
>
> Plan verification, application and rollback options.

> [card] [Transit pools](https://docs.axottle.com/en/connection-units/transit-pools.md)
>
> Own canvas pool and the continuation of the route.

> [card] [Balancing](https://docs.axottle.com/en/connection-units/balancing.md)
>
> Connection Distribution and Failure Behavior.

> [card] [Flow Guard](https://docs.axottle.com/en/connection-units/recovery.md)
>
> Manual plans and authorized auto-recovery.

> [card] [Failure Lab](https://docs.axottle.com/en/connection-units/failure-lab.md)
>
> Failure Modeling and Evidence Boundaries.

## Verification

Find Flow in **Configs**, open its used version and the time of the last check. For the new Flow, complete the [application](https://docs.axottle.com/en/connection-units/lifecycle.md), then check the health and real client connection.

## Rollback

Before use, you can reset a draft. For a working Flow, use [Version history or recovery plan](https://docs.axottle.com/en/connection-units/lifecycle.md#откат).

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.