No more operations to execute a scenario
This error appears when your organization runs out of operations allocated to your monthly limit based on your subscription plan.
In such a case, all your scenarios are paused and incoming webhooks are stored in the webhook queue.
How are operations calculated?
Every time your scenario is triggered it consumes one operation no matter how many data bundles (items) are processed/output by the trigger module.
Every action done by subsequent modules (usually one action per one data bundle/item) then costs one operation no matter how many data bundles/items the specific module outputs. More details on the above can be found in this documentation.
Please note that the operation consumption is greatly influenced by the scenario scheduling. As every scenario execution costs at least one operation no matter how many actions the scenario does, it is crucial to realize the minimum operations consumption before you schedule and activate the scenario.
E.g. setting the scenario to a 1-hour interval means it consumes at least 24 operations daily only to check whether there are some new items for processing. If you schedule your scenario to run every 5 minutes, you will need at least 2016 (60/5*24*7) operations weekly to operate it + operations needed for all the actions it does.