> For the complete documentation index, see [llms.txt](https://docs.creativeconners.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.creativeconners.com/docs/spikemark-6/running-cues/restore-cue.md).
# Restore Cue
The Restore Cue function helps you precisely reposition machines during show preparation and rehearsal.
## Purpose
Restore Cue allows you to move machines to their most recent target positions, ensuring that the machines are in the correct starting position. To avoid risking collisions, move each machine individually and make sure the travel path for each machine is clear before running the move.
## Why Individual Machine Restoration Matters
A typical scenario during rehearsals is that a director often request revisiting specific moments in the show. Consider a 10-cue production where you're currently at Cue 6, and the director wants to return to Cue 4. However, not all cues move every machine. In our example, lets pretend that only one machine moved in Cue 3, but we have 4 machines in our show. Simply re-running Cue 3 won't guarantee all machines are in the correct starting position for Cue 4.
By using Restore Cue, you can:
* Move all your machines to the correct starting position
* Move machines individually
* Prevent potential set piece collisions
## How to Restore a Cue
1. Right-click the cue header of the cue you want to restore - this is usually the cue just before the cue you are about to run again
2. Select "Restore Cue" to open the Restore Stage Window
3. Select machine(s) you want to move by:
* Single click for one machine
* Ctrl+Click for multiple non-consecutive machines
* Shift+Click for consecutive machines
4. Choose the Playback for loading moves
5. Set Speed, Acceleration, and Deceleration values
6. Click the Load icon to prepare the movement
7. Press GO on the loaded playback to execute
8. Repeat for each machine until all are correctly positioned
9. Close the Restore Stage Window after completing all moves
{% hint style="info" %}
Moving machines individually can help prevent potential collisions.
{% endhint %}
---
# 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.creativeconners.com/docs/spikemark-6/running-cues/restore-cue.md?ask=&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.
