MAKE WEBHOOKS
Make scenario deactivated — webhooks queue up, then drop
Make deactivates scenarios after repeated execution errors. Incoming webhook payloads then pile into a queue — and once that queue fills, payloads are dropped. Your senders keep getting acknowledgements the whole time.
Why Make webhooks fail silently
Error-triggered auto-deactivation
Consecutive execution failures (module errors, expired connections, rate limits) flip the scenario off without changing any visible config.
The queue hides the outage
Custom webhooks keep accepting payloads while the scenario is off — they sit in the webhook queue looking "received," which masks the failure from senders.
Queue caps mean real data loss
Queued payloads beyond the cap are discarded. A weekend-long deactivation on a busy hook silently loses thousands of events.
The fix
- 1
Check scenario state and the webhook queue
Open the scenario — look for the inactive state and check the webhook’s queue for backed-up payloads.
- 2
Fix the failing module
Check execution history for the erroring module — usually a dead connection or a changed API response shape.
- 3
Reactivate and drain the queue deliberately
Turn the scenario back on and let queued payloads process — but know anything over the cap is already gone.
- 4
Get alerted at deactivation, not discovery
Route the webhook through HookShield and monitor the Make URL’s forward responses — the moment forwards start queueing instead of executing, the pattern is visible.
DEAD-MAN'S SWITCH
Never find out about a dead webhook from a customer again
Point Make at a HookShield ingest URL. Every delivery is logged, signed, and forwarded — and if pings stop arriving, you're alerted before the silence becomes an incident.