Restore an earlier prompt version safely

Before you start

You need a prompt with at least one published version and permission to edit it. Decide which behavior you want to recover: the wording, the model settings, or both. Published versions preserve content and settings together, so restoring an older version can change more than the visible script.

Copy any draft text and settings you want to retain somewhere safe before starting. Saving a draft does not create a version-history entry, and saving restored work later replaces that saved draft. Restoring loads a selected version into the editor for review. It does not immediately replace the saved draft or switch live consumers back to that version. The existing published version remains in place until you publish again.

Compare and restore

1. Open the prompt's version history. Read the version numbers, change descriptions, model badges, and dates to identify a likely starting point.
2. When multiple versions exist, use From version and To version to compare the candidate with the current version. Inspect the content and settings, not just the opening lines. Use the fullscreen comparison if you need more room.
3. Choose Restore to draft on the version you want. The editor opens with that snapshot and a notice identifying the restored version. Check that the version number matches your intention.
4. If browser recovery offers unsaved changes, choose deliberately: recovering those changes replaces the selected restored content; discarding them keeps the selected version in the editor. Preserve any useful work before deciding.
5. Review the restored content, model, tools, and output settings. Correct facts that have become outdated. Use Test with the question that revealed the problem and a normal customer question.
6. Choose Save draft to keep the restoration without changing live behavior, or publish after reviewing the impact and adding a change description. A description such as restoring an earlier greeting explains the reason better than a version number alone.

Check the result

If you only save, the saved draft should contain the restored work while the published version remains unchanged. If you publish, the history gains a new version; previous versions remain available. Check a fresh automation reply and any response field mappings affected by the restored settings.

If you get stuck

A missing restore control may reflect your permissions. If the editor shows unexpected text, check whether browser recovery replaced the selected snapshot. If the restored prompt tests well but live replies differ, confirm you published it and consider whether the consumer is pinned or work was already queued. Restoring a prompt does not restore deleted Manychat fields, repair credentials, or change automation mappings. Review those dependencies separately before assuming the old behavior is fully recovered.

Recheck external knowledge and delivery

Restoring prompt settings does not restore earlier file-store contents or HTTP service data. Verify that the selected model and tools are still available, that referenced stores contain the intended documents, and that credentials can access them. Review automation-level audio/image/PDF preferences separately; they are not a rollback of the prompt script. Test the restored draft, publish deliberately, and check a new live reply through the intended route.

Related guides

• Drafts and publishing
• Create an automation
• Automation not replying