Cycles removal on October 1, 2026

Make will remove cycles from scenarios on October 1, 2026. Starting from this date, expect the following changes:

Until October 1, the Cycles per run setting is no longer visible in new scenarios. It's still available in existing scenarios that had more than one cycle configured.

If your scenarios were among the few using more than one cycle, Make will email you with a list of affected scenarios. If you didn't get an email, none of your scenarios are affected.

A cycle is one pass through all modules in a scenario. When you set multiple cycles, a pass repeats several times within a single scenario run, pulling data from the trigger module until no data records are left waiting.

For example, your trigger module is set to process 5 emails per run, but your inbox has 10 unprocessed emails. With one cycle, two scheduled runs return all emails. With two cycles, one run does.

You set the number of cycles per run with the Cycles per run setting in Scenario settings > Advanced settings.

This setting only applies to scheduled scenarios with trigger modules that have a field limiting the number of records per run. Instant scenarios and scenarios with search or action trigger modules don't use it.

Few Makers used cycles, and the setting was more confusing than helpful. In most scenarios that used more than one cycle, multiple cycles rarely took effect.

Removing cycles takes a rarely used option from Scenario settings and simplifies the engine that runs your scenarios. Fewer moving parts mean fewer edge cases and more predictable runs.

On October 1, 2026, the following changes also take effect in Tools settings that tie a value's lifetime to a cycle:

Here's what to expect, and when:

Your scenarios continue running without any action needed from you. Most scenarios behave the same as before.

If your scenarios have multiple cycles configured, you can:

If anything is still unclear, reach out to Customer Care with your questions.