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

# Diagnosis of Flow

> Static verification, live health, website availability, data freshness and incident history.

There are three different types of verification available for Flow: **Verification** Analyzes the configuration. **Health** It collects data from the route, and **Failure Lab** Calculate the consequences of possible refusal.

## Before use

Open **Check → Run the** check. Correct the taper's criticisms and review the warnings. Static check does not establish a real connection by the client and does not confirm the availability of an external destination.

**Apply Changes button** separately collects the application plan and shows dependencies and necessary confirmations.

## Working route

1. Open the tab **Health** of the desired Flow.
2. Run **Check + Logic**.
3. Check the overall estimate, time and version of the checks.
4. Discuss the sequence of checks by nodes and blocks, then the history of incidents and recovery.
5. If necessary, use **Collect logs** in the node log block.

**Update** rereads the stored data; this is not a new full run. For the yet unused Flow, there is no confirmation of a working client path.

## Data layers

| Level | What is checked by |
| - | - |
| L1 | Node Achievability |
| L2 | Condition of necessary services. |
| L3 | Connection Establishment. |
| L4 | Through passage along the route. |
| L5 | External regional availability with a connected provider. |
| L6 | Analysis of collected data via Axosun. |

When the bottom layer fails, the dependent top checks are not validated. The external provider error, the regional lock, and the lack of data are different situations. The Axosun analysis explains the available data, but does not replace the successful network test.

## Freshness and controversy

Health refers to the applied Flow image. Late response to check the old version should not replace the current state. Old or conflicting information requires re-checking, rather than automatically inferring "everything works."

The history of the events connects checks, configuration changes, and recovery. First, compare the failure time with the applications and the state of the nodes. Status "Applied" describes the deployment operation, not the result of all subsequent checks.

## Unavailable Sites and Risks

Flow Studio's review has a radar of unavailable sites and operational risks. Data collection about inaccessible sites is included in the settings of a particular Flow. This data helps to see problems with real-world destinations that a synthetic sample may not replicate.

Don't mix a proper synthetic check with a guarantee of availability of all sites. Check coverage, time, and source of measurements; no observation does not mean no problem.

## Comparison of Flow and External Reports

The Flow Studio review table compares deployments, redundancy, configuration discrepancies, resources, certificates, delays, pool participants, and regional availability. Use search, filters for problematic, unknown, or healthy Flows, and sort by attention required. Cell shows the value and cause; transition opens the corresponding Flow tab.

The risks of common nodes and pools show the area of influence on several Flows. Unknown and outdated values require new observations. In the **Health tab**, a separate [History Bscheck](https://docs.axottle.com/en/health/bscheck.md) with details of external checks and cost is available.

## Verification of the result

Run a fresh check after the fix, make sure it’s relevant to the current active version, and check with the client the exact route or site the complaint was made to.

## Rollback

Diagnostics and calculation of the Failure Lab do not change the route. Changing recovery is performed separately through the [Flow Guard](https://docs.axottle.com/en/connection-units/recovery.md) or [version history](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.