> 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-retry.md).

# \&retry

Control automatic retry/reconnect timing for lost streams

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

## Also controls

* `&retrytimeout` — minimum milliseconds to wait before attempting to recover a lost stream (default 5000ms)

## Options

Examples:

* `&retry=30` (seconds)
* `&retrytimeout=8000` (milliseconds)

| Parameter       | Value           | Description                                         |
| --------------- | --------------- | --------------------------------------------------- |
| `&retry`        | Integer seconds | Periodically re-queries streams and refreshes state |
| `&retrytimeout` | Integer ms      | Min wait before trying to recover a lost stream     |

## Details

* `&retry` schedules a periodic maintenance task that refreshes stream state (e.g., every N seconds). Lower bounds may be clamped (min \~10s internally).
* `&retrytimeout` sets how long VDO.Ninja waits before proactively trying to recover a missing stream. Minimum enforced is 5000ms.
* Useful for long-running overlays and multi-view pages where a guest might temporarily disconnect.

## Related

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

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

{% 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 %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.