> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/extensionsmanager/installation-guide/features/automatic-product-restarts.md).

# Automatic product restarts

The **Extensions Manager** includes a built-in **auto-restart feature** that helps maintain uptime and stability for your extensions.

If a product unexpectedly stops or crashes, the Extensions Manager will automatically attempt to **restart it**.\
This ensures that your extensions remain available without requiring manual intervention.

#### How it works

* The system continuously monitors the status of all running products.
* If a product becomes unresponsive or stops unexpectedly, it is restarted automatically.
* The restart process runs in the background and typically completes within seconds.

#### Notes

* Automatic restarts apply to **all running extensions** managed by the Extensions Manager.
* If a product repeatedly fails to start, the ExtensionsManager will eventually stop restarting this product automatically.
* You can manually stop or restart any product at any time from the **Product Overview**.


---

# 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.infotopics.com/extensionsmanager/installation-guide/features/automatic-product-restarts.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.
