> For the complete documentation index, see [llms.txt](https://prosbcdocs.telcobridges.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prosbcdocs.telcobridges.com/appendices/appendix-a-glossary/glossary-toolpack/glossary-tboamapp/master-slave/active-standby.md).

# Active/Standby

Active is the application instance operating the system; standby is the instance not currently performing that role. Compare Master/Slave.

### Active

Active is a state that indicates which application instance is operating the system.

### Standby

Standby is another instance state that indicates that the application instance is not performing any operations and is waiting to take over. (As opposed to [Master/Slave](/appendices/appendix-a-glossary/glossary-toolpack/glossary-tboamapp/master-slave.md) applications where the slave instance can still perform operations

<br>

### Example

Example: toolpack\_sys\_manager is an active/standby type application. The active toolpack\_sys\_manager is the only instance that takes action on the whole system, the standby toolpack\_sys\_manager waits to takeover if the active toolpack\_sys\_manager fails.


---

# 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://prosbcdocs.telcobridges.com/appendices/appendix-a-glossary/glossary-toolpack/glossary-tboamapp/master-slave/active-standby.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.