Make.com Made Crystal Clear · chapter 2: How Make Thinks: Scenarios, Modules, Bundles, Credits
Execution versus cycle
2026-10-20
The execution is the whole run; a cycle is one pass of data through the modules inside it. Max cycles, in scenario settings, defaults to 1.
Below: the paragraph from the book that builds this idea, then the diagram itself (Figure 2.3), and a recap. About a minute of reading.
One last pair of terms, because run history and several settings use them precisely. An execution is one full scenario run, from the moment it starts to the moment it finishes: one press of the play button, or one wake-up of the schedule. A cycle is one complete pass of data through the modules inside that run. Most runs are exactly one cycle, because the setting that allows more, Max cycles in the scenario settings, defaults to 1. Raise it, and a single run repeats its pass while more data is waiting, which is exactly how instant-trigger scenarios drain a queue of webhook events in chapter 4. Figure 2.3 puts the two words in one picture.
Recap
- The idea: The execution is the whole run; a cycle is one pass of data through the modules inside it.
- The picture: Figure 2.3, from chapter 2 ("How Make Thinks: Scenarios, Modules, Bundles, Credits") of Make.com Made Crystal Clear.
- Go deeper: the chapter builds this step by step, with recipes and sources at the end.
This diagram is one of many in Make.com Made Crystal Clear.
Every chapter opens with the gist, draws the hard ideas, and ends with recipes and sources.
Get the book
