Pausing or unpublishing an agent
Open the agent from Agents and choose Pause agent. The widget stops serving immediately, every setting is kept, and Resume agent puts it back.
Last checked against the running product on 30 August 2026.
Pausing is the right tool for taking the chat down for a while: a holiday shutdown, a pricing change you have not written up yet, a site migration. It changes nothing except whether visitors can reach the agent.
Open the agent
Agents in the sidebar, then the agent's card. The buttons are at the top right of its page.
Choose Pause agent
The status badge changes to paused and a line underneath says the widget is not serving this agent and its configuration is kept. The change is immediate: the widget stops answering on the next request it makes.
What a visitor sees
The launcher script still runs, but the panel reports that the assistant is unavailable rather than opening a conversation. If you would rather nothing appeared at all, remove the snippet from your pages instead.
Resume when you are ready
The same button now reads Resume agent. Nothing was lost while it slept: the public key in your snippet, the published date, the instructions, the branding and the knowledge sources are all exactly as they were, so the widget picks up where it stopped.
Edit while it is paused, if you want to
A paused agent is still listed, still readable and still editable. Resuming re-checks the same rules publishing applies, because the configuration may have changed while it was off the air.
| State | Serves visitors | Counts against the 10 published agents | Still in the portal |
|---|---|---|---|
| Published | Yes | Yes | Yes |
| Paused | No | No | Yes, fully editable |
| Draft | No | No | Yes, fully editable |
Unpublishing back to Draft has no button yet
The API can move a published agent back to Draft, but nothing in the portal calls it. Pause is the control that exists, and for taking an agent off the air it does the same job while keeping the slot free. If you specifically need the agent back in Draft, email info@ravan.ai.
There is no delete either
Archiving an agent exists in the API and hides it from every agent route, but the portal has no control for it. Pausing is what you have; conversations and leads already captured are unaffected either way.
If it still does not work
The pause button is disabled
Hover it and the tooltip explains why. Only a published agent can be paused; a draft was never serving anyone, so there is nothing to take down.
Resuming says a subscription is required
Resuming puts the agent back in front of visitors, which needs an active subscription — the same check publishing makes. Pausing deliberately makes no such check: you can always stop your agent. Open Billing.
Resuming says the published agent limit is reached
A paused agent frees its slot, so something else may have taken it while this one slept. Pause an agent you are not using, then resume this one.
Resuming is rejected over a field
The agent was edited while it was paused and no longer passes the publishing checks — most often the allowed domain was cleared. Fix the named field in the editor and resume again.
The launcher is still on your site after you paused it
That is the snippet, which is still in your pages and still runs. What stops is the answering: the agent status is checked on every widget request, including each message, so a conversation already open cannot send another one. If you want nothing at all to appear, take the snippet out of your pages as well.
Related articles
- Getting startedCreating your first agentAnswer four setup questions to get a drafted agent, or build one by hand in Agents. Either way it stays a draft until you add an allowed domain and publish it.
- TroubleshootingMy widget is not showing upFour causes account for nearly every missing widget: the agent is not published, the domain is not approved, the snippet is not really on the page, or the Chat toggle is off. Check them in that order.
- OperatingReading conversations and leadsConversations holds every stored transcript with its page metadata; Leads holds the contacts captured with consent. Both screens are read-only: you cannot type a reply into a visitor's chat from here.