No more credits to execute a scenario
In such a case, all your scenarios are paused, and incoming webhooks are stored in the webhook queue.
Once new credits are allocated either by the purchase of extra credits or reaching a new usage reset (once per month), your scenarios get automatically resumed, and all the unprocessed webhooks and unchecked records are processed.
How are credits calculated?
Every time your scenario is triggered, it consumes one credit, 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) costs one credit, no matter how many data bundles/items the specific module outputs. Some Make’s built-in AI features may, however, consume more credits as we align billing with the actual AI usage costs. This concept is known as “Dynamic credit usage”
A complete overview of credits & operations can be found in this documentation.
Please note that the credits consumption is greatly influenced by the scenario scheduling.
As every scenario execution costs at least one credit, no matter how many actions the scenario does, it is crucial to realise the minimal credit consumption before you schedule and activate the scenario.
E.g. setting the scenario to a 1-hour interval means it consumes at least 24 credits 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) credits weekly to operate it + credits needed for all the actions it does.