> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Emergency Stop

> Stop all of Neo for your account in one action: no agent runs, and Neo calls none of your systems until an admin resumes it.

The emergency stop halts all of Neo for your account at once. Use it when a vendor reports a breach, when an agent does something it should not, or when you want Neo out of your systems right now. One action stops everything, and one action brings it back.

Open it from [**Settings → General → Emergency stop**](https://dashboard.neoagent.io/settings#emergency-stop). Admins and owners can stop and resume Neo; everyone else in your workspace sees whether it is stopped. You can also ask the Neo Support Agent to stop or resume Neo, and it asks you to approve first.

## What stops

Within 10 seconds of a stop, on every Neo server:

* **No call leaves for your systems.** Neo calls none of your PSA, RMM, documentation tools, Microsoft 365 and your customers' Microsoft 365 tenants, Exchange PowerShell, custom API connections or Slack.
* **No agent runs.** Triggered and scheduled agents start no run, and a run already going ends at its next step. Each skipped run shows on the [Executions](https://docs.neoagent.io/product/executions.md) page with the reason.
* **Nothing reaches your end users.** Neo sends them no message, email, text or call. Your Neo phone numbers stop answering new calls; a call already in progress runs until it ends, and its agent reaches none of your systems.
* **Chat agents take no messages.** Someone who writes to one is told at once that Neo is paused; nothing they send is answered later. The [Neo Support Agent](https://docs.neoagent.io/chat-agents/neo-support-agent.md) keeps answering, so an admin can ask it to resume Neo.
* **Scheduled syncs skip your account.** Ticket, company and document syncs wait for the resume.

> [!NOTE]
>
> The stop keeps your connections and stored credentials as they are. You do not need to disconnect any integration or revoke any key, and nothing needs reconnecting after you resume.

## What waits for the resume

PSA updates that arrive during the stop, such as a new ticket or a status change, are kept for at least a month: Neo keeps PSA updates for the current and the previous calendar month, so a stop longer than that loses its oldest updates. When an admin resumes Neo, they go through Neo in the order they arrived, and your triggered agents act on them as if they had just happened. Neo reads each ticket's history when it processes the update, so no change is missed.

A scheduled agent does not catch up its missed runs. Its next run after the resume runs as normal.

## Resume Neo

Press **Resume Neo** in the same section. Neo calls your systems and runs agents again within 10 seconds, and starts processing the held PSA updates.

## Who did what

For admins and owners, the section lists the latest stops and resumes: who pressed each one and when. Other members see whether Neo is stopped and since when. A stop or resume within 20 seconds of the last one is refused, so the first reaches every part of Neo. Each one also shows in the member's [Activity History](https://docs.neoagent.io/product/rbac.md#activity-tracking). From the API, `GET /public-api/emergency-stop` returns the same.

## From the API

| Request | What it does |
| - | - |
| `GET /public-api/emergency-stop` | Whether Neo is stopped, who stopped or resumed it last, and the latest 20 stops and resumes |
| `POST /public-api/emergency-stop/stop` | Stops Neo |
| `POST /public-api/emergency-stop/resume` | Resumes Neo and processes the held PSA updates |

Both writes need an admin or owner, or an API key with no acting user.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.