> 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/mixer-scene-parameters/and-scenerestore.md).

# \&scenerestore

Restores a guest's selected scene assignments after reconnecting

Director Option! ([`&director`](/advanced-settings/director-parameters/director.md), [`&room`](/advanced-settings/setup-parameters/room.md))

## Details

Add `&scenerestore` to the director URL to let the main director restore a guest's manual scene assignment after that guest disconnects and rejoins.

Example:

```
https://vdo.ninja/?director=ROOMNAME&scenerestore
```

This is useful when guests are manually assigned to scene outputs such as `&scene=1`, `&scene=2`, or `&scene=3`, and a guest drops because of a poor connection.

When enabled, the main director creates a temporary restore lease when a guest is placed into a scene. If that guest reconnects with the matching restore token while the lease is still active, the director can reapply the previous scene selection.

The lease auto-renews while the guest remains connected, so long-running sessions continue to be restorable. After a disconnect, or after the last scene action for that guest, the lease expires after 15 minutes. If the director hangs up, disconnects, or otherwise revokes the guest, the lease expires immediately.

`&scenerestore` is opt-in. It does not bypass room authentication, director approval, queue/hold modes, or the normal director trust checks.

This option is sometimes mistaken for `&scenestore` or "scene store". The current parameter name is `&scenerestore`. It is a reconnect helper for scene assignments, not a permanent cloud scene database.

## Related

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

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

{% content-ref url="/pages/-MZfzezMF7\_FyjAq8Dze" %}
[How to get permanent links](/guides/how-to-get-permanent-links.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/mixer-scene-parameters/and-scenerestore.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.