> For the complete documentation index, see [llms.txt](https://docs.vdo.ninja/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vdo.ninja/advanced-settings/settings-parameters/and-autorecover.md).

# \&autorecover

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))

## Options

Examples:

* `&autorecover`
* `&autorecover=1`
* `&autorecover=0`

| Value                     | Description             |
| ------------------------- | ----------------------- |
| `1`, `true`, `on`, `yes`  | Enable recovery bundle  |
| `0`, `false`, `off`, `no` | Disable recovery bundle |

## What it toggles

When enabled, this currently enables:

* `autoRelay` behavior (equivalent to using [`&autorelay`](/advanced-settings/turn-and-stun-parameters/and-autorelay.md))
* Adaptive disconnect timing
* Automatic WHEP fallback signaling where WHIP/WHEP settings are available

When disabled (`&autorecover=0`), those three assists are turned off. Baseline ICE recovery still runs. A later explicit `&autorelay=1` can re-enable only relay escalation because the dedicated flag is parsed after this bundle.

{% hint style="info" %}
Auto-relay itself now defaults enabled, while adaptive disconnect timing and automatic WHEP fallback remain off by default. Use `&autorecover=1&autorelay=off` when you want those other bundle features without forced-relay escalation.
{% endhint %}

## Details

* Intended for links where guests may roam networks or experience intermittent P2P failures.
* Best used with [`&p2pfailtimeout`](/advanced-settings/settings-parameters/and-p2pfailtimeout.md) and [`&peerrecoversteps`](/advanced-settings/settings-parameters/and-peerrecoversteps.md) to tune aggressiveness.
* Keeps direct P2P as the first connection path; the bundle changes recovery behavior only after a connection degrades or fails.

## Usage examples

* Conservative: `?room=show123&autorecover=1&p2pfailtimeout=12000&peerrecoversteps=3`
* Aggressive: `?room=show123&autorecover=1&p2pfailtimeout=6000&peerrecoversteps=5`

## Related

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

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

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


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.