How to do it
- Pause all Choose Pause all agents in the app. The workspace shows as Paused.
- Check what is held Scheduled posts stay in the queue but do not publish while paused.
- Fix the problem Revoke a key, edit or reject drafts, or tighten guardrails.
- Resume Choose Resume. Held posts are released, and any whose time has passed go out on the next run.
When to use it
- An agent is drafting the wrong thing at volume.
- A news event makes your scheduled posts look tone-deaf.
- You suspect a key leaked and want everything still while you rotate it.
- An incident is ongoing and you want no marketing posts. See incident communication.
What pausing does
| While paused | Behavior |
|---|---|
| Queued and scheduled posts | Held, not published |
| Agent schedule requests | Refused with HTTP 423 |
| Approve and schedule | Refused with HTTP 423 |
| Agent drafts | Still land in the inbox for review |
| Auto-publishing agents | Stopped, like every other agent |
Before you resume
Posts whose time passed while paused are released when you resume. If a held post no longer makes sense, reject it or move its time first.
From the API
Owners can call POST /v1/workspace/pause with { "paused": true } or false. That makes the switch scriptable from an incident runbook. See API and SDK.
The kill switch glossary entry covers the idea more broadly.
Frequently asked questions
Does the kill switch delete anything?
No. It holds posts and refuses new schedules. Nothing is deleted, and Resume releases the queue.
Can an agent resume the workspace?
No. Pausing and resuming need the owner.
What happens to a post that was mid-publish when I paused?
A post already accepted by the network stays live. The switch holds everything that has not started publishing.