Make adds scenario version descriptions and a new toolbar: what changed in October 2026

What did Make change in scenario version control on October 7, 2026?

On October 7, 2026 Make redesigned the scenario toolbar and added descriptions to saved scenario versions. You can now save a version with a note, read version history like a changelog and restore the right one. Both changes are on all plans.

The source is Make's release note Improved scenario toolbar and version control, dated October 7, 2026, and the updated scenario version control guide, also updated October 7. We read both on October 30, 2026. Six days earlier, on October 1, Make also removed the Cycles per run setting from every scenario, which we cover below because it changes how some scheduled scenarios behave.

How does Make scenario version history work now?

Press Ctrl + Shift + S or choose Save a version, then add a description. Make keeps each saved version for 60 days, and the latest one until you save a newer one. A restored version must be saved by hand.

The release note puts it in one line: "You can now add descriptions to scenario versions, so you can iterate safely without creating clone scenarios." The version control guide adds the details that matter in practice:

• Each version shows its description, the name of the person who saved it, and the date and time.
• Retention. "Make stores each saved version for 60 days, except the latest version, which it keeps until you save a newer one."
• Restore is two steps. Pick the version in Version history, click Restore version, then click Save. "Make doesn't save the restored version automatically."
• Scenario recovery brings back unsaved changes after a browser crash or a closed tab, from a blueprint Make saves in the background. Make says plainly that it "is not an autosave feature", and the recovered changes still need a manual save.

Before this change, a common way to try an edit safely was to clone the scenario, change the copy, then switch over. That doubled the scenarios to keep track of, and the clone's history said nothing about why it existed. A described version does the same job inside one scenario.

What changed when Make removed cycles on October 1, 2026?

From October 1, 2026 every Make scenario run completes one cycle. Scheduled scenarios that used several cycles to drain a backlog now process the same data across more runs. Make emailed the owners of affected scenarios.

Make's cycles removal note explains the old behaviour with an example: a trigger set to 5 emails per run with 10 waiting needs two runs with one cycle, and one run with two cycles. With cycles gone, it is always the first case. The note also removes two related options: "After one cycle" in the Increment function, and the "One cycle" variable lifetime in Set variable and Set multiple variables.

If you did not get an email from Make, the note says none of your scenarios were affected. If you did, Make lists two fixes: raise the maximum number of results the trigger processes per run, or shorten the schedule interval so the scenario runs more often. Both can change your credit use, because a polling trigger costs a credit for every check. Our FAQ on what happens when Make runs out of credits covers what to watch.

What does this mean for your business?

You can now change a live Make scenario with a named restore point and a record of who changed what. That lowers the risk of edits to scenarios that handle leads, orders or invoices, as long as someone saves versions on purpose.

Version history only helps if versions are saved with useful notes, and it only reaches back 60 days for anything except the latest version. For scenarios your business depends on, we treat it as one layer next to two others: an exported blueprint kept outside Make, and alerts when a run fails. Make's event subscriptions, launched October 8, 2026, can send those alerts on the Teams and Enterprise plans; our report on Make's October AI Agent and event subscription update covers them.

Here is the routine we follow when we change a live scenario:

1. Save a version before touching anything, described as "Before" plus the reason, for example "Before adding VAT field to invoice sync".
2. Make the change and test with Run once on test data, now next to Save in the new toolbar.
3. Save a version describing the change, including the ticket or request it came from.
4. Watch the next real runs in scenario history. If a run fails, restore the "Before" version, click Save, and investigate afterwards.
5. Export the blueprint of anything critical at least monthly, because versions older than 60 days are deleted.

If you run Make scenarios that several people edit, or you have scenarios built by someone who has since left, this is a good moment to audit them. Our Make.com automation agency service starts with a free audit of your scenarios, and our guide to who owns automations and data explains why the blueprints should sit on your side.

Questions about the Make version control update

Is Make version history available on the Free plan?

Yes. Make's October 7, 2026 release note lists both the new toolbar and version descriptions as available on all plans. The 60-day retention rule in the version control guide does not mention a plan difference either. Our FAQ on whether Make.com is free lists the limits that do differ on the Free plan.

How long does Make keep old scenario versions?

Make's version control guide says each saved version is kept for 60 days, except the latest version, which stays until you save a newer one. Anything you may need to return to after two months should be exported as a blueprint and stored outside Make, for example in a shared drive or a code repository your team controls.

Does restoring a Make version change the live scenario straight away?

No. Make's guide says it does not save the restored version automatically. You click Restore version, then Save in the toolbar to keep it. Until you save, the scenario that runs is the last saved one. After an emergency restore, open the scenario again and check the version shown is the one you meant to keep.

Do I need to do anything about the October 1 cycles removal?

Only if Make emailed you a list of affected scenarios. Make says scenarios keep running with no action needed, and most behave the same. If yours relied on several cycles to clear a backlog, raise the trigger's maximum results per run or run the schedule more often, and check the effect on your monthly credits.

Sources

• Make release note, Improved scenario toolbar and version control (October 7, 2026; new toolbar, Save as version, descriptions in version history, all plans), read October 30, 2026.
• Make Help Center, Scenario version control (updated October 7, 2026; Ctrl + Shift + S, 60-day retention, restore then save, scenario recovery), read October 30, 2026.
• Make release note, Cycles removal on October 1, 2026 (announced August 13, 2026, updated October 29, 2026; affected settings and fixes), read October 30, 2026.
• Make release note, Introducing event subscriptions (October 8, 2026), read October 30, 2026.
• Make release notes, 2026 (dates of the October 2026 entries), read October 30, 2026.