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, 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.
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.
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
