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

> What to do with an outdated plan, application error, pool change and recovery lock.

Start with three questions: is the draft saved, what version is used, and what fresh checks apply to it, editor error, application, and health of the route running should be dealt with separately.

## Diagnostic procedure

1. Open **Check** and eliminate blocking configuration remarks.
2. Click **Apply changes to**, read the plan and reasons for failure.
3. After application, open **Health** and run a fresh check with logs.
4. To recover, go to the **Recovery** tab and study the pre-check of the selected plan.

## Model situations

| Symptoms of | What to Test for |
| - | - |
| Canvas is not saved | Link tolerance, no cycles, CDN assignment and revision conflict. |
| Plan not compiled by | Physical nodes, transport parameters, ports, exits and route conditions. |
| Plan changed after viewing | Reassemble it: draft, settings or dependent pool changed. |
| Not ready DNS | Correct the record or consciously confirm the shown domains in the application dialogue. |
| Balanced Mode Requires | Confirmation Read Remnawave JSON Subscription Setting Change. |
| Pool saved, itinerary old | Save changes the directory. A running Flow requires a new plan and application. |
| Pool is not compiled by | Check continuation, dead ends, cycles, nested Pool Node and conditions on either side of the pool boundary. |
| Node participates in another Flow | Check the impact report, config compatibility and ports. Sharing does not mean automatic removal from another Flow. |
| Version applied, but tests failed | Disassemble partial result, failure layer and validation time. Status of application does not equal health. |
| All pool candidates are not available | With `fail_closed` lock expected.Restore candidate; direct bypass requires explicit customization. |
| Auto-Recovery Not Launched by | Operating Version, Policy Permits, Plan Version, Data Freshness, Confirmations, Pause, Limit and Suspension. |
| After switching back the old route | Check the following manual application: automatic switching leaves the custom draft the same. |
| Remove not completed | Reconnect with Remnawave and repeat cleaning through the shown button. |

## The rollback loaded, but the route didn't change

**Versions → Roll back** restores the picture to a draft. Check it and press **Apply changes to**. Rollback through a confirmed Flow Guard plan may include an application; read the steps of a specific operation.

## Website Unavailable With Healthy Flow

Look at the radar of inaccessible sites, the results of external checks and the actual customer path. Synthetic test is validating its purpose, so its success does not prove the availability of any site, an inaccessible external sample provider also does not prove a route blocking.

## Verification

The plan is tested, the expected version is active, there is no incomplete application or recovery, and fresh data and customer verification confirm the desired path.

## Rollback

Use the [version history of](https://docs.axottle.com/en/connection-units/lifecycle.md#откат). Before re-acting after a partial failure, find out which steps have already been completed.

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.