Operations

Every time a module in a scenario performs an action, it uses one operation. If a module outputs multiple bundles of information (like a List module returning multiple records), it makes the following module run once for each bundle, processing each record separately. The total number of used operations for a module equals the number of performed actions.

All the types of modules can use from one to many operations, depending on their place and function in the scenario:

There are a few exceptions of modules when Make does not use the operations:

In this scenario, Make gets the list of the Top 10 songs of an artist you select, and adds it to the list of the songs you liked.

Once the execution of a scenario is completed, Make displays the number of operations performed by each module in the little white circle above the module.

In this example, the first Spotify module returned 10 songs and performed 1 operation while getting the information. Each song is returned as a bundle of information, so the next module has to work with 10 bundles.

The second Spotify module had to add each of the 10 songs to the playlist, requiring it to perform this action 10 times. As a result, the module processed 10 bundles and used 10 operations.

The run of this scenario required 11 operations in total.

In the example above you can see how to count operations for a scenario during one run. But it is also important to know how many operations your scenario is using in total.

Scheduling your scenario will make it consume operations every time it runs. For example, if your Spotify scenario is scheduled to run every hour, that would equal to 264 operations a day (11x24).  If you schedule it to run every 5 minutes, it will consume 3168 operations per day (11x24x12). That's why it's important to schedule your scenario carefully. You can reduce the number of used operations by scheduling some scenarios to run less frequently.

Every scenario run uses at least one operation because the trigger module needs to check for updates. Even when no new data is retrieved, these check runs still add to your total operation count, as the trigger uses an operation each time it checks according to the schedule. You can view all the check runs from the History tab in your scenario. If you don’t see them, ensure that the Hide check runs toggle is off.

You can also check how many operations your scenario has consumed in total without calculating anything. You can easily find this information in the list of scenarios or the scenario history.

From the list of scenarios

When you open a list of scenarios you can see how many operations each scenario has consumed under its name. If you hover over the number you can see the date when the count started (the beginning of the usage period).

For yearly subscriptions, the label displays the reset date, but the data represents an aggregated usage within the last 60 days.

From the scenario history

To open the scenario execution history click on the scenario from the list of scenarios. Under History on the right, you can see the number of operations consumed for each scenario run.

Similarly, you can switch to the History tab and see the number of consumed operations for each run there in a table format.

Note

When a regular execution ends with a warning or error, an incomplete execution is created. Any attempts to fix it are tracked in the Incomplete Executions tab, with each attempt consuming operations. These operations add to the total used by the scenario and are included in the operations usage displayed in the list of scenarios, even though they aren't visible in the History tab. You can view the operations used to resolve an incomplete execution in the incomplete execution details. Note that, by default, the storage of incomplete executions is disabled, but you can enable it individually for each scenario.

While it is important to know how many operations each scenario consumes it is also important to know how many operations your Organization and each Team within the Organization use. This can be easily checked from both Organization and Team dashboards.

To open the dashboard, click Organization or Team in the left-side navigation.

From the Organization dashboards it is also possible to see the limits you have according to your plan, how many operations were used during the current period, and to check the options of purchasing additional operations if needed.

When you run out of operations, your scenarios will pause until additional operations are added or the next billing cycle begins. Incoming webhooks will be queued based on your available webhook storage and processed once your scenarios resume with the new operations. Additionally, scenarios that poll for data will search for available records since the last successful run.

We'll notify you when you're approaching 90% and 95% of your purchased operations. This way, you can ensure you have enough operations to meet your needs or take action to prevent your scenarios from pausing.

Here’s what you can do if you run out of operations before the next billing cycle: