Skip to main content

Validate and publish a draft

Publishing promotes the saved draft into an immutable production snapshot. It does not automatically activate a paused agent or configure its delivery channel.

Pre-publish review​

Before selecting Publish:

  • confirm the editor save state is successful;
  • run the planned draft scenarios;
  • resolve configuration errors and investigate warnings;
  • verify variables, knowledge, and exact function markers;
  • confirm integrations are connected and least-privileged;
  • inspect the draft cost estimate; and
  • arrange the production smoke test and rollback owner.

Publish​

  1. Select Publish.
  2. Review the Configuration check.
  3. Enter an optional Version Name.
  4. Enter an optional Version Note describing the change and reason.
  5. Select Publish Version.

Before sending the publish request, the editor forces pending draft changes to save. If that save fails, publication is cancelled.

Validation behavior​

The server requires an existing draft and validates the current configuration schema and architecture/provider compatibility. Errors block publication. Warnings can remain visible without necessarily blocking it, so review them deliberately.

Examples of blocking conditions include invalid or unavailable architecture components and required configuration that cannot run. Chat Agents in Beta are also blocked from publishing while a voice-only Call Transfer function is attached.

Prompt warnings and configuration validation solve different problems. A configuration can be structurally publishable while still containing weak business rules or unsupported factual claims.

Atomic publication​

The publish operation:

  1. loads the active draft;
  2. snapshots its function attachments and granular integration tools;
  3. marks the draft published with time, name, and note;
  4. archives the previously published version;
  5. updates the agent's published-version pointer and runtime fields; and
  6. clears the draft pointer.

When the editor refreshes, it creates a new working draft from the published version so editing can continue.

After publishing​

Publication changes the configuration selected by new production conversations. It does not rewrite a voice call or website session already in progress.

For inbound voice delivery, confirm the correct number remains assigned and the agent is Active, then place a new call. Publishing is not a substitute for live verification.