Versioning & Publishing
Drafts, the publish lifecycle, and restoring versions.
Edit agents as drafts, publish them when ready, and restore earlier versions at any time.
Publishing removes the draft
Publishing turns your draft into the new published version and then removes the draft. That is normally invisible — you keep editing and a new draft appears.
It matters in one case: if you attached a staging or test space to a portal and set that space to show the agent's draft, visitors are reading the draft directly. Publishing removes it, so the portal stops working for them until you make your next edit.
You do not have to avoid this — showing a draft to testers is what that setting is for. But because the failure appears on a visitor's screen rather than yours, publishing now warns you when it affects a portal, and names which one. Make any edit to create a new draft and the portal works again.
Restoring an older version
Restoring copies an old version back into your draft, where you can review it before publishing.
A restore (or a publish) can be refused if the stored settings contain a value the platform can no longer run — most often a maximum call duration outside the allowed 1–120 minutes, saved before that limit was enforced. The error names the field; correct it in the builder and publish again. Nothing is changed on your behalf, so what you publish is always what you reviewed.