ContactBook a call

Fix broken Make

Fix a Make scenario that keeps erroring, deactivating or running twice

We read your scenario history and incomplete executions, find why runs fail or repeat, and fix the scenarios in your account with the right error handlers. Then we add alerts and write down what each scenario does.

Start with
The $500 Automation Audit
We read
Scenario history and incomplete executions
Access
Team member access, never your password

In short

Make gives you good tools for failure, but they are off or unused in most scenarios we are asked to fix. Storing incomplete executions is off by default, so a failed run can stop and roll back with nothing kept to retry. A scenario can be set to deactivate after a number of errors in a row, and one that starts with an instant trigger is deactivated after the first error. Error handlers (Retry, Resume, Skip, Commit and Rollback) decide what happens next. We read the history, set these up deliberately, and add alerts.

What we hear about Make

  • The scenario deactivated and webhooks piled up unprocessed.
  • Records are created twice after a retry.
  • Operations run out before the end of the month.
  • A data store has grown and nobody knows what is in it.
  • The scenario runs on a schedule that no longer fits the business.

Why Make scenarios fail, and what Make does about it

The platform behaviour below comes from the Make Help Center, listed under sources.

SymptomWhat Make doesWhat we change
Scenario deactivatedDeactivated after the set number of consecutive errors. A scenario with an instant trigger is deactivated after the first error.Fix the failing module and add error handlers so expected errors do not stop the scenario.
Failed run lostWith incomplete executions off (the default), a failed run stops and rolls back. With them on, it is kept to resolve or retry.Turn on incomplete executions where a lost run matters, and resolve the backlog.
Errors with nothing storedSome errors never create an incomplete execution, for example an error on the first module or when storage is full.Add a Retry handler to the first module and watch storage.
Wrong error handlerRetry, Resume, Skip, Commit and Rollback each end the run differently. Retry needs incomplete executions turned on.Choose the handler per module, so temporary errors retry and data errors reach a person.
Operations run outEach module run counts as an operation, and a module handling many bundles runs once per bundle.Filter early, aggregate where possible and cut polling that finds nothing.
Out of order or running twiceWith sequential processing off, runs carry on to schedule regardless of errors. With it on, each run finishes before the next starts.Turn on sequential processing where order matters, and add a check before records are created.

How we fix a Make organisation

How we work in your account

What it costs

Every engagement starts with the audit, so you know what is broken and what it costs to fix before you commit to anything else. Payment by Stripe, PayPal, Wise, Razorpay, Infinity or bank transfer.

Full pricing · The audit · Care plans

Automation Audit
$500Credited in full to the fixes or the build. We read the run history, list every fault by risk and give you a fixed price in writing.
Fixes or rebuild
From $1,000Workflow builds and repairs start here. The statement of work fixes the price and the currency before we start.
Care plan
From $50 a monthMonitoring, error alerts, a monthly look at failed runs and small changes, after the fixes are live.
Automation team
$999 a monthFor a steady queue of smaller requests across several platforms and workflows.

Related pages

Questions buyers ask

Before anything changes, the Automation Audit gives you the fix list and a fixed price.

Why did my Make scenario turn off?

Make deactivates a scenario after the number of consecutive errors set in its settings. A scenario that starts with an instant trigger, such as a webhook, is deactivated after the first error. Fix the failing module, then reactivate it.

Why is my Make scenario running twice?

Common causes are two scenarios on the same event, a webhook sender that retried, or a run retried from incomplete executions after part of it had already worked. We check the history and add a lookup before records are created.

What are incomplete executions in Make?

Failed runs that Make keeps so you can fix the problem and retry or resolve them. Storing them is off by default and is turned on in scenario settings.

Which Make error handler should I use?

Retry for temporary faults such as connection or rate limit errors, Resume to carry on with a substitute value, Skip to drop the bundle, and Commit or Rollback to stop the run. Retry needs incomplete executions turned on.

Why are we running out of Make operations?

Every module run is an operation, and modules after an iterator run once per bundle. Polling triggers that check often also add up. We filter early and cut runs that do nothing.

How much does it cost to fix a Make scenario?

The $500 Automation Audit comes first and is credited in full to the fixes. You get a fixed price per fix in writing. Workflow builds and repairs start from $1,000.

Do you need my Make password?

No. You invite us to your Make organisation or team as a member and remove us when we finish.

Can you take over scenarios someone else built?

Yes. We document each scenario, fix what is broken and hand over a runbook.

Should we move from Make to n8n?

Sometimes, when operations costs have climbed or you need self-hosting or code steps. The audit says so if it would cost less.

Platform behaviour changes with new releases. Checked against the official help pages on 16 November 2026. Sources:

Show us what is failing

On a triage call you show us the workflows that are failing and what they cost you, and we explain what the audit would cover. The call is free.

Book a triage call

Cookie preferences

Choose what this site may use on your device. You can change this at any time from “Cookie settings” in the footer.

Strictly necessary

Keep the site working and remember the choices you make here. These cannot be switched off, and none of them track you.

Always on
What this includes (4)
NameProvider PurposeDuration
sbd-consentThis site Remembers your cookie choices12 months
Vercel Web AnalyticsVercel Inc. Counts page views in aggregate. Sets no cookie and stores nothing on your deviceNone
ticker-dismissed, sbd-note-offThis site Remembers that you closed a notice or language tipUntil the tab closes
sbd-voice-resume, sbd-voice-prefillThis site Carries a voice conversation across pages, only if you start oneUntil the tab closes

Analytics

Tell us which pages are read and where visitors leave, so we can improve them. IP addresses are anonymised and nothing is used for advertising.

What this includes (2)
NameProvider PurposeDuration
_gaGoogle Analytics (Google LLC) Distinguishes visitors with a random ID13 months
_ga_FPXDMQPRV1Google Analytics (Google LLC) Keeps the session state for this site13 months

Functional

Embedded services that set their own cookies. Without them the site still works; you get a link to open the service instead.

What this includes (1)
NameProvider PurposeDuration
Booking calendarCal.com Inc. Shows live availability and books the call on the booking pageSet by Cal.com

Advertising

Not used. This site has no advertising, retargeting or social media tracking, and we never sell data.

Not used

Questions about your data: hello@smallbaydigital.com