What happens when Make runs out of credits?

What happens when Make runs out of credits?

The next module that needs a credit fails with OperationsLimitExceededError, the run ends, and Make switches off the scenario's schedule straight away. Webhook calls wait in the queue up to its limit, and nothing else runs until credits are added.

That is the short version from Make's own Help Center and pricing page, read October 30, 2026. The detail matters, because the fix is more than buying credits: scenarios that Make switched off may need checking one by one. If your account keeps hitting the limit, our Make automation and repair service page explains how we rebuild scenarios to use fewer credits. This page covers what stops, what waits, and how to get running again.

What stops and what waits when Make credits hit zero?

Scheduled and instant scenarios stop. Incoming webhook calls are queued up to your queue limit, then rejected. Polling triggers pick up missed records on their next successful run. Running out of data transfer has the same effect as running out of credits.

There is one gap in Make's documentation. The pricing page FAQ says scenarios "won't continue to run, until credits are added again", which reads as if they resume on their own. The errors and warnings guide says OperationsLimitExceededError is fatal and Make "immediately disables the scenario scheduling". Neither page says whether Make switches a disabled scenario back on for you. So after adding credits, open your scenarios list and confirm each one is active.

How do you get Make scenarios running again after credits run out?

Add credits by buying extras, turning on auto-purchasing or upgrading, then check every scenario is switched on, let the webhook queues drain, and retry any incomplete executions. Extra credits need a paid plan.

1. Add credits. On a paid plan, go to Org, then Subscription, then Buy extras. Manual purchases come in units of 1,000 and cost 25% more than the credits in your plan, card or debit card only, according to Make's extra credits guide. On Free there is no extra-credit option: you wait for the monthly reset or upgrade.
2. Or upgrade. Make's change your subscription guide converts unused credits into a dollar discount on the new plan. Make's own example: Core at $113.85 for 150,000 credits is $0.000759 a credit, so 160,000 unused credits become a $121.44 discount.
3. Switch scenarios back on. Open the scenarios list and check the Active toggle on each one. Any scenario that was running when credits ran out may now be inactive.
4. Check the webhook queues. Queued calls run once the scenario is on. If a sender received 400 "Queue is full", that data never reached Make and has to be sent again from the source app.
5. Retry incomplete executions. If the scenario stores incomplete executions, the run that failed at zero credits is waiting there. The incomplete executions guide covers retrying or resolving them.

Step 4 is the one people miss. For the status codes a sender sees, our guide to a Make webhook that stops working lists each one and its fix.

How does Make credit auto-purchasing work, and what does it cost?

With auto-purchasing on, Make buys 10,000 credits each time your plan's credits run out, at 25% above your plan's per-credit price. It stops when the extras equal your plan's own credit count, so an 80,000-credit plan auto-buys at most 8 times.

Make's extra credits guide sets the rules: purchases come in units of 10,000, card payment only, and the cap per cycle equals the credits in your subscription. It also warns that "exhausting data transfer can trigger an auto-purchase even if there are still credits left." The pricing page lists auto-purchasing for the Core, Pro and Teams plans.

The cost of one auto-purchase depends on your plan's per-credit price. We used the three prices Make quotes in its own Help Center:

The worst case is the cap. On the 150,000-credit Core tier, auto-purchasing can run 15 times in one cycle: 150,000 extra credits for 15 x $9.49 = about $142, on top of the $113.85 plan. If you hit the cap regularly, a higher tier is cheaper: Make's own guide recommends it, because higher tiers have lower per-credit prices. The $338.13 price is from Make's November 2025 plans and pricing note; confirm your tier on Make's pricing page before you buy.

If a card payment for credits fails, Make says your scenarios pause until you update the payment method. For a failed subscription payment, its payment failure guide gives a seven-day grace period before the subscription is cancelled.

Will Make warn you before your credits run out?

Yes, by email to the organization owner and admins. Make always emails at 90% and 100% of your credits, and at 75% only when you are using them faster than the month is passing.

Make's credit tracking guide gives the 75% rule as an example: 75% used with 40% of the month gone triggers an email; 75% used with 75% of the month gone does not. The same guide lists where to see usage: the organization dashboard (average daily use and credits left), the Credit Usage table (credits per run), the scenarios list (credits per scenario for up to the past 30 days) and each module's output bubble.

Enterprise accounts can also cap credits per team. Make's team credit limits guide says a team that reaches its limit has its scenarios paused until the reset or until more credits are allocated, with emails at 75%, 90% and 100%. That keeps one busy team from stopping everyone else's scenarios.

The emails only go to owners and admins. If nobody in that group reads them, set a forwarding rule to whoever looks after your automations.

Do unused or extra Make credits carry over to next month?

No. Plan credits and extra credits expire at the end of the billing cycle. On annual Pro and Teams plans they last the year; on Core they reset monthly even with annual billing. Downgrades carry unused credits over; cancellations do not.

Sources: Make's extra credits, monthly and annual subscriptions, change your subscription and cancel your subscription guides, read October 30, 2026.

How do you stop a Make account from running out of credits?

Find the scenarios that use the most credits, then cut credits per run: use webhooks instead of frequent polling, filter before expensive modules, aggregate instead of looping, and move long code or AI steps where they cost less.

Make's guide to how features use credits gives the rules that matter most:

• A polling trigger costs a credit per check, even when nothing is found. A trigger checking every 15 minutes uses 2,880 credits in a 30-day month before doing any work. A webhook trigger waits for free.
• Action modules cost a credit per bundle. Deleting 10 rows costs 10 credits. A search module returning 10 rows costs 1.
• Some modules are free. Routers, filters, error handlers, the Functions modules and the Scenarios modules (Call a subscenario, Start a scenario) use no credits.
• Aggregators save credits. Make's own operations guide example cuts a run from 11 operations to 3 by sending one summary email instead of ten.
• Code and AI are priced differently. Make Code costs 2 credits per second of run time, and Make's AI Provider adds token credits on top of the operation. Our research on Make AI credit costs by model shows how much the model choice changes a run.

When a workflow needs many steps per run, n8n workflow automation may cost less, because n8n Cloud bills once per run instead of per step. Our Make vs n8n pricing comparison shows where the crossover sits.

More questions about running out of Make credits

Does Make charge you automatically when credits run out?

Only if extra credits auto-purchasing is turned on. Then Make buys 10,000 credits at 25% above your plan rate each time you run out, up to the number of credits in your plan per cycle. With it off, nothing is charged and your scenarios stop until you buy credits, upgrade or reach the next reset. Auto-purchasing is listed for Core, Pro and Teams.

What is OperationsLimitExceededError in Make?

It is the error a module returns when your organization has no credits left. Make's errors guide calls it fatal: the run ends with an error and Make disables the scenario's schedule immediately, without waiting for the usual three consecutive errors. The fix is to add credits or upgrade, then turn the scenario back on and retry any stored incomplete executions.

Do webhook calls get lost when Make runs out of credits?

Not at first. Make queues incoming webhook calls up to your queue limit, 667 items per 10,000 credits with a 10,000 maximum, and processes them once credits are added. Calls that arrive after the queue is full are rejected with HTTP 400 "Queue is full", and that data has to be sent again from the source app.

Can we limit how many credits one team or person uses?

Yes. Make's private spaces, available on all plans, let admins set a monthly or yearly credit limit for each member's space; when a member reaches it, only the scenarios in that space pause. Enterprise accounts can also cap credits per team, so one busy team cannot stop the rest of the organization.

Can you find out why our Make credits run out early?

Yes. Our audit is free: we list each scenario's credit use, find the polling triggers, loops and AI steps behind it, and show what a rebuild would save. A small fix or rebuild of two or three scenarios is about $1,000 at the time of writing, and fixes to what we build are free for 6 months. See what support looks like after a build.

Sources and further reading

• Make Help Center, Fix errors and warnings (OperationsLimitExceededError and DataSizeLimitExceededError are fatal and disable scheduling immediately), read October 30, 2026.
• Make Help Center, Overview of error handling (number of consecutive errors, default 3, does not apply to these errors), read October 30, 2026.
• Make pricing page (what happens if you run out of credits, webhook queueing, polling catch-up, auto-purchasing on Core, Pro and Teams, credits expire at end of term), read October 30, 2026.
• Make Help Center, Webhooks (667 queue items per 10,000 credits, 10,000 maximum, 400 Queue is full), read October 30, 2026.
• Make Help Center, Extra credits (units of 1,000 or 10,000, 25% additional cost, auto-purchase cap, data transfer trigger, card only), read October 30, 2026.
• Make release note, Adjustments to plans and pricing (November 6, 2025: 25% on all extra credits, $338.13 for 500,000 credits example), read October 30, 2026.
• Make Help Center, Change your subscription (upgrade discount, downgrade credit transfer, Core $113.85 for 150,000 credits example), read October 30, 2026.
• Make Help Center, Monthly and annual subscriptions (Core credits reset monthly on annual billing), read October 30, 2026.
• Make Help Center, How to track credits (75%, 90% and 100% notification emails, where usage is shown), read October 30, 2026.
• Make Help Center, Credits per team management (Enterprise team limits pause the team's scenarios), read October 30, 2026.
• Make Help Center, How features use credits (credits by module type, modules with no credit cost, Make Code 2 credits per second), read October 30, 2026.
• Make Help Center, Private spaces (available on all plans; per-member credit limits pause that member's scenarios), read October 30, 2026.
• Make Help Center, What to do if your payment fails (seven-day grace period), read October 30, 2026.

Make changes billing rules from time to time. If a number here differs from what your account shows, Make's current documentation wins.