Prompts / Article

Save a prompt draft and publish a new version

Understand what saving changes, test your working draft, and review automation impact before publishing.

Before you start

Open the correct prompt in the intended workspace and make sure you have permission to edit and publish it. Know which automation uses it. If a prompt is already serving customers, record a realistic test question and its expected answer before making a change.

A draft is work in progress. Save draft stores your edits without changing the published version. Publishing creates a new immutable version with the prompt content and its saved model settings. Tests of a working draft can therefore differ from live replies that still use the published version.

Save, test, and publish

Open the prompt editor and review the current content and settings. Make a focused change, such as correcting a policy or improving the greeting, so you can identify its effect.
Use Save draft when you want to preserve the change without releasing it. Check the save result before leaving. Browser recovery can help with unsaved changes, but it is not a substitute for deliberately saving your work.
Choose Test to try the working draft. Repeat your baseline question, then try a question affected by the change. Check tool behavior and response structure if your automation expects particular fields.
Choose the publish button when ready. In the confirmation, enter a meaningful description of what changed. Read the proposed version and the impact review, including saved automations that reference this prompt.
Review warnings about response paths, destination types, or unavailable metadata. Publishing does not automatically repair field mappings. If needed, cancel, inspect the automation, and return after you understand the change.
Confirm publication. Verify the new version in the prompt's version history, then send a fresh end-to-end test through the automation.

Check the result

The version history should show a new published version with your change description. Requests for the latest version and new automation runs use the new version. Consumers pinned to an older version and queued snapshots keep their saved version. Publishing does not unblock a prompt whose API access is blocked; that access must be allowed separately.

If you get stuck

A disabled confirmation can mean missing content, invalid settings, an empty change description, or an incomplete impact review. If the impact changed, review the updated details and confirm again. The review uses saved workspace metadata, not a live Manychat check, and cannot list external API consumers. After changing output fields, review mappings and test actual delivery even if the comparison looks compatible. If the new behavior is wrong, restore a previous version to a draft for review.

What a prompt version does not freeze

A published version preserves its prompt and settings, but external dependencies can still change. File-store contents can be added or removed independently; credentials and HTTP services may become unavailable. Review those dependencies when an unchanged prompt starts behaving differently. Approved website knowledge attached in AI Studio is fixed to the draft's selected version and is not refreshed automatically.

After comparing models or drafts, publish the exact content and settings you selected. The mapping preview does not send its draft output; live automation tests use the saved published automation. Check its media-processing preferences and response flow as well as the prompt version.