# 🔥 Feature Spotlight: Upgraded Scenario version control **URL:** \ **Category:** News\ **Tags:** product-updates, scenario\ **Created:** [October 7, 2026, 9:00am UTC](https://community.make.com/t/feature-spotlight-upgraded-scenario-version-control/116853 "2026-10-07T09:00:13Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![a\_garcia](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/a_garcia/32/94084_2.png) [@a\_garcia](https://community.make.com/u/a_garcia)\ **Post date:** [October 7, 2026, 9:00am UTC](https://community.make.com/t/feature-spotlight-upgraded-scenario-version-control/116853/1 "2026-10-07T09:00:13Z")
## **Never guess your scenario history again with version descriptions** Rolling back a scenario shouldn’t rely on remembering a timestamp, and testing new workflows shouldn’t require building messy “(copy)” clones. To build fast without breaking trust, you need a clear, traceable history of exactly what changed and why. That’s why, alongside the recent [Scenario Toolbar upgrade](https://community.make.com/t/feature-spotlight-scenario-toolbar-redesign/116731), we rolled out a key update to give you exact control over your scenario’s changes directly within the Scenario Builder: **Save as version** and custom **version descriptions**. ## **🆕 What’s new** - 📝 **Leave a clear audit trail:** Use the new _Save as version_ option to explicitly attach a specific description to your save state, logging the exact tweaks you made. - 🧪 **Test and iterate easily:** Want to add a new module or change how bundles flow through a complex route? Save a descriptive version first. If the new logic doesn’t perform as expected, you have a clearly labeled fallback. ![toolbarredesign_runsave_v2](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/6/b/6bb19d012fa0c84c2cd4f6ae17c7eb94ae0f8a80.gif) - 🕰 **Review your history with context:** Instead of just a list of timestamps, your version history is now a readable changelog. View your custom descriptions for every save, and edit past descriptions to keep your documentation tidy as your scenario evolves. - ⏪ **Restore with confidence:** No more guessing which version is the one you were looking for. Read your custom descriptions, identify the exact version you need, and restore it from the bottom toolbar in seconds. ![toolbarredesign_versionhistory_v1](https://europe1.discourse-cdn.com/flex013/uploads/make/original/3X/8/4/846b6d4abb2efab366eaa82cf5b8a4929bdae0ff.gif) ## **🚀 Real-world use cases** - 🔀 **Say goodbye to “(copy)” drafts:** Stop cluttering your workspace with duplicate scenarios just to test a new logic. Save a version like “V1 - Stable active version,” keep building in the same Scenario Builder, and restore V1 instantly if needed. - 🔧 **Troubleshooting errors:** If a previously stable scenario suddenly fails, review the version descriptions to find the last known working state and revert immediately to minimize downtime. - 🤝 **Seamless team handoffs:** When transferring ownership of a scenario to a colleague, your descriptive versions act as a built-in changelog so they understand the business logic behind every update. - 🏗 **Documenting iterative builds:** Break down large automation projects into milestones, saving versions like “V1 - Base webhook connected” or “V2 - Added Slack alerts” to track your progress and pick up exactly where you left off. ## **✅ Availability** Available on all Make plans, including Free. Whether you are experimenting with new routing logic, troubleshooting an error, or handing a scenario off to a teammate, these descriptions ensure that anyone reviewing the history instantly understands the business context behind the change. Happy automating! 🟣 Andrés from Make ## 📚 **Helpful Resources** > 👉[Scenario version control documentation](https://help.make.com/scenario-version-control) ---
**Author:** ![Sarah\_D](https://avatars.discourse-cdn.com/v4/letter/s/ebca7d/32.png) [@Sarah\_D](https://community.make.com/u/Sarah_D)\ **Post date:** [October 7, 2026, 9:16am UTC](https://community.make.com/t/feature-spotlight-upgraded-scenario-version-control/116853/2 "2026-10-07T09:16:12Z")
This is really useful thank you. How long will versions stay available for and/or how many pervious versions will we be able to see? ---
**Author:** ![a\_garcia](https://dub1.discourse-cdn.com/flex013/user_avatar/community.make.com/a_garcia/32/94084_2.png) [@a\_garcia](https://community.make.com/u/a_garcia)\ **Post date:** [October 7, 2026, 2:47pm UTC](https://community.make.com/t/feature-spotlight-upgraded-scenario-version-control/116853/3 "2026-10-07T14:47:07Z")
So glad it’s helpful! Regarding your questions: versions are **stored for up to** **60 days** , and there’s **no limit** on how many versions you can save or view as long as they are within that window. Hope it is clearer now 😄