Publish and version
Objective. Validate a tested draft and release it as a versioned flow snapshot without changing an in-progress live conversation.
Prerequisites
- A saved bot draft that you have tested in the simulator.
- Editor or owner access to the bot.
- A connected WhatsApp channel only when you want the published version to handle live WhatsApp traffic. Publishing itself does not require Meta credentials.
Publish a validated draft
- 1In the editor top bar, check whether the bot is Not published or has a version with draft edits, then select Publish.
- 2Review the Publish bot dialog. It checks the draft for blocking errors and warnings. Resolve every blocking error before publishing; warnings are shown but do not stop the release.
- 3Select Publish in the dialog. Fluenta creates the next version for the bot and reports the published version when the request succeeds.
Know what a publication contains
A publication is an immutable snapshot of the full bot definition: every flow and the mainFlowId that identifies the entry flow. The editable canvas remains a draft, so changes after publishing do not affect the published version until you publish again.
Understand live conversations and rollback
- 1Publishing a new version does not rewrite a live conversation. A conversation already using a published version continues with that version; the runtime moves a stale session to the latest version only when the flow signals that it should reset and reruns that inbound message as a fresh session.
- 2Fluenta stores versioned immutable snapshots, but the editor has no self-service publication history or rollback control. Restoring a previous snapshot is currently a support request.
- 3If you need an immediate correction, fix the draft, test it again, and publish the corrected draft as the next version. Do not look for a rollback button that is not in the editor.
Expected result
Expected result. The editor reports a new published version, its full flow definition is captured as a publication snapshot, and later draft edits remain separate until another publish. Existing live conversations are not retroactively rewritten.
Common errors
- Publish is blocked by errors.
- Read the blocking errors in the Publish bot dialog, then correct the referenced flow or node. A flow can also be blocked when it uses a missing plugin or an enabled connector that is not configured.
- My canvas edit is not reflected in the live bot.
- Canvas changes are draft edits. Test the change, then publish a new version before expecting it to affect future live flow execution.
- An existing conversation did not switch to the new version.
- That is expected. An in-progress conversation continues on its current published version rather than being rewritten by a new release.
- I need to roll back to an earlier publication.
- There is no self-service rollback control. Previous publications are immutable snapshots, and restoring one is currently a support request. For a correction you can make now, fix and test the draft, then publish the next version.