# \&peerrecoversteps

General Option! ([`&push`](/advanced-settings/setup-parameters/push.md), [`&room`](/advanced-settings/setup-parameters/room.md), [`&view`](/advanced-settings/mixer-scene-parameters/view.md), [`&scene`](/advanced-settings/mixer-scene-parameters/scene.md), [`&director`](/advanced-settings/director-parameters/director.md))

## Aliases

* `&p2precoversteps`

## Options

Example: `&peerrecoversteps=4`

| Value   | Description                  |
| ------- | ---------------------------- |
| Integer | Max number of recovery steps |

## Details

* Default is `3`.
* Allowed range is clamped to `1` through `6`.
* Higher values allow more retries before the peer is closed/rebuilt.
* Lower values fail fast and rely on fresh reconnection sooner.

Current recovery ladder (simplified):

1. Attempt ICE restart.
2. Rotate ICE/TURN preference and attempt relay escalation, then ICE restart.
3. Additional attempts continue up to the configured step limit; with `&autorecover` and WHIP/WHEP configured, auto-fallback signaling may be attempted for eligible peers.

## Usage examples

* Balanced default-like behavior: `?room=show123&peerrecoversteps=3`
* Very persistent recovery: `?room=show123&autorecover=1&peerrecoversteps=6`

## Related

{% content-ref url="/pages/RXoyUCs4znWVHC6X5eLP" %}
[\&p2pfailtimeout](/advanced-settings/settings-parameters/and-p2pfailtimeout.md)
{% endcontent-ref %}

{% content-ref url="/pages/zGrl2B1uV4Vm3OkTolja" %}
[\&autorecover](/advanced-settings/settings-parameters/and-autorecover.md)
{% endcontent-ref %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.vdo.ninja/advanced-settings/settings-parameters/and-peerrecoversteps.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.