Make Problems & Issues
Real user-reported problems, complaints, and limitations for Make. Based on analysis of 13 signals.
Overall score: 62/100
Issues by Category
Why does Make use so many credits?
Every module action costs a credit, and polling triggers (Watch modules) spend a credit on every check even when nothing new is found. A trigger polling every minute burns roughly 44,000 credits a month on its own, and loops through iterators multiply usage per bundle.
Make switched from operations to credits (AI modules cost more)
On August 27, 2025 Make replaced operations with credits as its billing unit. Standard actions still cost 1 credit, but features using Make's built-in AI provider are billed by actual usage and can consume several credits per run, so AI-heavy scenarios got more expensive.
Make extra credits now cost 25% more, Core capped at 300k credits
From November 6, 2025 extra credits cost 25% more than plan credits whether bought manually (previously no premium) or via auto-purchase (previously 30%). Core was capped at 300,000 credits per month, pushing heavier users to Pro.
Make webhook not triggering the scenario
One of the most common community threads: webhooks that only fire on 'Run once', stop working after weeks, or never receive data from the sender. Causes range from the scenario being off or scheduled instead of instant, to wrong data structure, to webhooks auto-deactivated after 5 days unused.
Make scenarios turn off automatically after errors
Make disables a scenario's schedule after several consecutive errors and immediately on fatal errors like data size limits. This protects credits but means automations silently stop until someone notices and re-enables them.
Make outages disabled scenarios and dropped webhooks
Incidents in Sept 2025 (all scenarios, ~2 hours), Dec 2025 (Cloudflare), March 2026 (US2 webhooks), July 2026 (~250 scenarios disabled for about 29 hours) and Oct 2026 (Scenario app failures) left automations stopped or webhooks unprocessed, often requiring manual re-enabling.
Make scenarios time out after 40 minutes
Paid plans stop a run after 40 minutes (5 minutes on Free) with ExecutionInterruptedError, leaving remaining bundles unprocessed. Large syncs must be split into chained scenarios or batched.
Make hits rate limits (429) on busy scenarios
Instant triggers and bulk processing frequently hit third-party API limits (Webflow, Google Drive), and the app's limit is shared across all your scenarios. Make itself also caps incoming webhooks at 300 requests per 10 seconds.
Make editor is slow with large scenarios
Reviewers mention UI sluggishness, lag and occasional freezes when scenarios grow to many modules.
Make connections keep expiring (invalid refresh token)
Gmail, Google Drive and Microsoft 365 connections regularly fail with 'invalid_grant' or 'Invalid refresh token, please reauthorize'. Some users hit it weekly because their Google Cloud app is in testing mode, and in some threads reauthorizing doesn't fix it.
Make support is slow and billing refunds are hard
Trustpilot reviewers describe weeks without replies and refunds only after pushing, including a case of credits charged multiple times due to platform lag. Community users note the support ticket form is the only direct contact channel.
Make has a steep learning curve (bundles, iterators, aggregators)
Reviewers consistently say Make takes days to weeks before building complex scenarios comfortably. Concepts like bundles, iterators, aggregators, mapping and filters confuse non-technical users who expected Zapier-level simplicity.
Make errors are hard to diagnose
Capterra reviewers report that errors are hard to trace and fix, and community threads show generic messages like BundleValidationError usually point to an empty value from an upstream module rather than the module that failed.
Regret Patterns
Common reasons users regret choosing Make.
Credits gone in days because of polling triggers
Users set Watch triggers to every minute or every few minutes and burn most of the monthly allowance on empty checks.
Automations silently stopped after auto-disable
A scenario hit consecutive errors or an outage, Make turned it off, and nobody noticed for days.
Expected Zapier-simple, got a learning curve
Beginners switch for price, then struggle with bundles, iterators, aggregators and data mapping.
Connections keep needing reauthorization
Google and Microsoft connections expire with refresh-token errors, breaking scenarios until reconnected.
Billing disputes with slow support
Users charged extra credits by lag or auto-purchase report long waits and resistance to refunds.
AI scenarios cost more after the credits switch
Scenarios using Make's AI provider consume variable credits, making costs less predictable than flat operations.
When Make Breaks Down
Specific scenarios where Make fails or underperforms.
High-frequency polling triggers
Each check costs a credit; a 1-minute poll uses ~44,000 credits a month before doing any work.
Large data syncs over 40 minutes
Runs end with ExecutionInterruptedError and leftover bundles are not processed.
Burst webhook traffic
More than 300 requests per 10 seconds return 429, and full queues reject data with 'Queue is full'.
Many scenarios hitting the same API
Rate limits are shared across scenarios, so 429 RateLimitError appears under load.
Google apps in OAuth testing mode
Refresh tokens expire about weekly, so connections fail with 'invalid refresh token'.
Platform outages
Webhooks received during incidents may not be processed and scenarios may be auto-disabled.