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

# Node's life cycle

> How to read the status of the node, remove it from traffic, update the state and delete through the panel.

The status of the node combines Remnawave status, the results of the checks and the heartbeat of the agent, and control is performed on the page of a specific node.

## Statuses

| Status in | Panel Value |
| - | - |
| **Scheduled** | Node added, installation not yet started |
| **SSH Check passed** | Server available, connection options checked by |
| **Installation** | Installation |
| **Activated** | Node runs |
| **There are problems.** | The panel found a problem. |
| **Out of traffic** | New load from the node is removed before maintenance |
| **Error** | Installation or verification ended with error |
| **Removed** | Node deleted |
| **Imported** | Node imported from Remnawave |

## Update.

1. Open **Nodes** and select the server.
2. Click **Update** on the right side of the header.
3. Wait for the check to be completed.
4. Check status, heartbeat and fresh events on the tab **Review**.

To check the entire park, open the list. **Nodes** and press **Run the check.**.

## Remove the node from traffic

1. Open the node page → **Settings**.
2. Change **Traffic status** to `draining`.
3. Press **Save**.
4. Open those using the Flow node and remove it from the respective input or transit blocks.

Employment is indicated by a warning in the Flow constructor. There is no separate employment table in the panel.

## Get the node back to work.

Open up. **Settings**Get the old one back. **Traffic status**Save the changes and press **Update** in the title of the page.

## Remove the node

1. Make sure that node is no longer assigned to Flow blocks.
2. On the node page, click **Delete**.
3. Check the data in the dialogue and confirm the action.

If the node is still in use by the circuit, the panel will block the deletion and show dependence. Go back to the corresponding Flow and change the binding.

> [!WARNING]
>
> Recovery of the remote node via the interface is not provided. For temporary maintenance, use `draining`.

## Verification

> [!TIP]
>
> After status change, open **OZZZ**OURZ: the new label should be displayed in the title, and the action should be displayed in the **tab Journal**.


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