Skip to main content

Test and troubleshoot the agent lifecycle

Use a disposable paused agent for lifecycle testing. Keep production delivery disabled until draft, publish, and activation checks pass.

  1. Create one inbound voice agent and one Chat Agent in a test workspace.
  2. Open each editor and confirm a draft exists and autosave reaches Saved.
  3. Change the prompt, model, and one attachment; confirm the unpublished indicator.
  4. Run the editor test and verify it uses the changed draft.
  5. Publish with a version name and note; confirm the previous publication becomes historical.
  6. Change the draft again without publishing and verify a new live interaction still uses the published version.
  7. Restore an older version, confirm it is only a draft, then publish it as a new version.
  8. Duplicate the agent and confirm it is paused, unassigned, and has no inherited publication history.
  9. Delete only the disposable copy and verify shared knowledge and functions remain.

Common problems​

Agent limit reached​

Paused, active, and draft agent records count toward the workspace plan limit. Delete an unneeded agent only after reviewing its records, or upgrade the active workspace plan.

Save remains on Saving or shows Save failed​

Check network connectivity and the active workspace. Do not publish or navigate away. Wait for reconnection, make a small change, confirm Saved, then reload and verify the stored draft.

Publish says no draft exists​

Open the agent editor to initialize a draft, make or verify the intended configuration, wait for autosave, and retry.

Publish is blocked by configuration errors​

Follow the first reported diagnostic. Common causes include an unavailable model, an invalid architecture-specific field, an out-of-range timing value, or malformed configuration. A Chat Agent must also detach voice-only Call Transfer functions.

Publish button says no unpublished changes​

The saved draft currently matches the published prompt, model, voice, configuration, and function/tool snapshots. Confirm you edited the intended agent and workspace.

Agent cannot start​

Publish it first. A voice agent also needs an assigned active phone number. A Chat Agent must be active before its website deployment can be enabled.

Draft test works but live behavior is old​

Saving and testing do not publish. Publish the draft, then start a new call or Website Chat session. Existing conversations remain pinned to the version they started with.

Restoring a version did not change production​

Restore creates a draft. Test and publish that draft to promote it.

Function changes are missing in production​

Confirm the function is attached in the working draft and its exact prompt marker is present, then publish. Production uses the function/tool snapshot captured during publication.

Duplicate has no number or live status​

This is expected. A duplicate is paused and unassigned. Review, publish, assign or deploy, and activate it separately.

Deleted logs or leads are missing​

Agent deletion is permanent and explicitly deletes associated calls and leads. Shared knowledge, functions, integrations, and the unassigned phone-number resource remain, but agent-owned operational history does not.