> For the complete documentation index, see [llms.txt](https://docs.holoplot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.holoplot.com/holoplot-control/maintaining-the-system/processor-failover.md).

# Processor failover

Processors can function as redundant pairs: one as Main and the other as Backup. Set up these pairs in Settings → Processors. Failover status does not influence processor health, although processor health can initiate automatic failover.

### Automatic failover

Automatic failover requires an assigned Backup Processor. HOLOPLOT Control switches to the other Processor when:

* The active Processor health becomes 🟠 Error or 🔴 Critical.
* The active Processor stops streaming audio.
* The active Processor stops responding before the failover timeout expires.

A short timeout (up to 10s) applies before switching. Recovery during that period cancels the pending failover. The target Processor must be healthy.

{% hint style="warning" %}
Automatic Processor failover is bidirectional from OS 2.6.3.
{% endhint %}

### Manual failover

An assigned Backup Processor enables manual failover. Open **Settings** → **Processors**. Open the pair’s three-dot menu. Then select **Force failover**.

Manual failover takes effect immediately. It can switch in either direction.

{% hint style="warning" %}
**Known issue:** Automatic failover triggers when a Processor health state exceeds **Warning**. You can initiate manual failover for devices with a health state of **Error** or better. As a result, manually failing over to an unhealthy Processor immediately triggers automatic failover.

**Workaround:** Unpair the healthy Processor before debugging or testing the unhealthy Processor.
{% endhint %}

<figure><img src="https://1870956965-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEWZvA6Ecdn48SRkbJ1C8%2Fuploads%2FfntnqMcVbvDKFh5maBeg%2FMaintenace_DeviceStatus_Processor-ForceFailover.png?alt=media&amp;token=bcab46b5-4117-4919-b4cb-3e7bad964453" alt="The Force failover action in the Processor pair menu" width="375"><figcaption><p>Manual failover</p></figcaption></figure>

### Find failover events

Failovers appear as **System** events in the Event Log. Filter the log by **System**. See the [Event Log](/holoplot-control/maintaining-the-system/device-events-list.md) for every failover event.


---

# 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.holoplot.com/holoplot-control/maintaining-the-system/processor-failover.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.