Short answer
Why Did My Make Scenario Use Too Many Operations?
Make operation use spikes when modules emit many bundles, iterators multiply downstream work, searches return broad result sets, or error retries repeat modules. Inspect scenario history bundle counts module by module, find where the count expands, then narrow searches, aggregate earlier, and prevent unnecessary retries.
Common causes
- A search module returns every matching record instead of one result.
- An iterator expands a large array before several downstream modules.
- The scenario polls frequently even when there is no useful work.
- An error handler retries a persistent rather than temporary failure.
Diagnostic steps
- Open a high-operation execution and compare operation counts after each module.
- Locate the first large bundle expansion and inspect its search limit or array input.
- Filter before iterating and aggregate before performing repeated downstream writes.
- Set retry rules for transient failures only, then compare usage over several scheduled runs.
Example
A search returns 500 contacts and an iterator sends each through three modules. Restricting the query to changed contacts prevents 1,500 unnecessary operations.
Caveats
Reducing schedule frequency can delay business-critical processing. Optimize bundle scope before changing service expectations.