Bot capacity, saved versions and rollback

Who this guide is for: customer ADMINISTRATORS who own bots. You need a plan that includes bots and, for publishing and rollback, a seat with the bots:write permission (see the bots plan note — Basic excludes bots entirely).

This guide walks you through three connected things you will meet as a bot owner: the plan's active-bot capacity, the saved versions every publish creates, and rolling back to an earlier version when a published flow needs undoing. Every button name, message and alert below matches what the test saw on screen.

About the pictures and examples. All screenshots and examples in this guide come from an isolated, synthetic test business used for product acceptance testing. Names like "SYNTHETIC capacity versions2906" and keywords like "QC2906…" are simulated test data, not real customers. The test recorded no message sends, no wallet, invoice or subscription changes — nothing live was delivered. This guide covers only this capacity/versions/rollback journey — it makes no claim about other product journeys or about parity with any other provider set.

How capacity works

The Bots screen always shows where you stand. With every slot taken it reads, verbatim:

"Plan capacity: 5 of 5 active published bots in use — flow starts this month: 1/10000 — at capacity: publishing refuses while every slot is taken; drafts stay safe and published bots keep running"

Three things follow from that sentence:

Step 1 — Publishing at capacity is refused (and that is safe)

  1. Open Bots from the Workspace sections navigation.
  2. Click the draft bot you want to publish. Its Bot editor panel opens.
  3. Click Publish.
  4. Instead of publishing, the editor shows an alert, verbatim:

"ACTIVE_BOT_LIMIT_REACHED — Active bot limit reached: this plan includes 5 active published bots. Unpublish or archive a bot to free a slot, or keep the flow as an unlimited draft. Plan Starter (v5). Choose a larger plan or free capacity to continue — your data is preserved and there is no automatic charge."

Your draft is untouched, your published bots keep running, and there is no automatic charge. Recovery is your choice: free a slot (Step 4) or change plans with your administrator.

Publish refused at capacity, desktop 1440px

Publish refused at capacity, mobile 390px

Step 2 — Look at saved versions

Every publish freezes the flow verbatim under its version number. As the Versions panel explains: "every publish freezes the flow verbatim under its version number, and runs pin the version they executed — the last 50 versions per bot are kept."

  1. Open a published bot. Scroll to the Versions heading.
  2. Each row shows the version (for example v3), when it was published, who published it, and its size in nodes and edges, with two buttons: View and Roll back.
  3. Click View version 3 (the current published version) to inspect it.
  4. Click View version 2 (an older, saved version). The detail opens marked: "version 2 · published by api at … · 2 nodes · 1 edges — read-only pinned snapshot", listing Nodes (verbatim) and Edges exactly as stored. There are no editable fields — a saved version can only be read.
  5. Click Close to return to the editor.

Viewing the current published version, desktop 1440px

Viewing a saved read-only version, desktop 1440px

Viewing a saved read-only version, mobile 390px

If the version detail fails to load (for example the connection drops), an error appears in the detail area. Recovery is simply: click that version's View again — the test verified the retry loads the snapshot and the error clears.

Step 3 — Roll back to a saved version

Rollback takes an old version's content and re-publishes it as a new version. As the screen repeats: "rollback re-publishes an old version's content as a NEW version — history is never rewritten."

  1. In the Versions list, click Roll back to version 2 on the row you want. (This also works from the keyboard: the test tabbed to the button and pressed Enter.)
  2. The row expands into an inline confirmation — "roll back to this version?" — with two buttons: Confirm rollback and Keep.
  3. Choose: - Keep to cancel. The confirmation closes, no request is sent, and nothing changes — the test verified this against the database. - Confirm rollback to go ahead.

Rollback confirmation with the SCOPE_DENIED refusal, desktop 1440px

If your seat is read-only, the rollback is refused with an alert, verbatim: "SCOPE_DENIED — this action requires the "bots:write" scope for your seat." Nothing changes. Ask an administrator, or use a seat that has the bots:write permission.

  1. After a confirmed rollback, the editor shows a status message, verbatim: "rolled back from v2 — republished as NEW version 4; history is immutable, the old entry stays". The Versions list gains a new row — v4 · by rollback:2 — while the v2 and v3 rows stay exactly as they were, and the bot's run history is untouched.

Confirmed rollback republished as new version 4, desktop 1440px

Confirmed rollback republished as new version 4, mobile 390px

Worth deciding carefully: rollback never erases or rewrites the version you are leaving — it adds a new version on top. If you later change your mind again, you roll forward to another version the same way. Nothing is lost, but the version number always moves up.

Step 4 — Free a slot and publish the refused draft

When capacity refused your draft, the fastest recovery is to free a slot:

  1. In the bot list, open a published bot you are willing to pause.
  2. Click Back to draft. The bot's status badge changes to draft.

    This is a real decision: a bot back in draft stops firing — as the editor's "How it runs" note says, "Draft bots never fire." Its keywords will not answer customers until you publish it again.

  3. Open the draft that was refused at capacity and click Publish. The badge changes to published.
  4. Reload the page and reopen the bot — the badge still reads published; the slot transfer is durable, not just on-screen.

Draft published after freeing a slot, desktop 1440px

Step 5 — Run history

The Runs panel under Versions lists every recorded run of the bot: "every recorded run of this bot — click a row for its pinned trace (the steps the runtime persisted, verbatim)." Each run row shows its outcome, the keyword that fired it and the time (in the test: a no_consent run, meaning the consent gate correctly sent nothing to an opted-out contact). Runs stay attached to the exact version that executed them, including across rollbacks.

If your plan does not include bots

On a messaging-only plan (Basic), the Bots screen's capacity line shows bots are excluded, and both creating and publishing are refused with an alert, verbatim:

"BOTS_NOT_IN_PLAN — Bots are not included in the Basic plan — it is messaging only. Your data, conversations and contacts are preserved; choose a plan that includes bots to create automations."

Basic plan refusal with data preserved, desktop 1440px

Nothing is deleted: the test verified the business's contacts, conversations, messages, wallet, invoices and plan renewals were byte-for-byte unchanged after the refusal.

What this guide does NOT claim (kept honest)

This guide documents the accepted capacity/saved-version/rollback journey only. It does not claim anything about other journeys, whole-product completion, live WhatsApp/Meta delivery, or equivalence with any other bot set or provider.


Evidence record (kept for honesty). Chief acceptance CT-BOT3021 (CHIEF_ACCEPTED_COUPLED_CAPACITY_VERSION_ROLLBACK_COMPONENT, 23 October 2026, 1 of 1 test passed) on app source 4c16b03512d41f6283be5ec14dfe7df2cfa6030d. The screenshots used here are listed with their acceptance IDs and SHA256 checksums in assets/ASSETS-MANIFEST.json.