MAKE WEBHOOKS
Make incomplete executions — payloads stuck in limbo
Incomplete executions are Make’s quiet failure mode: a module errored mid-run, the execution parked itself, and the payload waits for manual attention. Nothing retries, nothing alerts unless you configured it — the data just stops flowing.
Why Make webhooks fail silently
Mid-execution failures park the run
A module error with incomplete-execution storage enabled stops the run in place — often by design, but nobody watches the pile.
No automatic retry on parked runs
Incomplete executions need manual resolution or an auto-retry setting — otherwise they accumulate forever.
Backpressure upstream
While executions stall, the webhook queue behind them grows — eventually hitting the drop cap.
The fix
- 1
Check the incomplete executions tab
Scenario → Incomplete executions. The count is the honest measure of how backed-up you are.
- 2
Enable sequential/auto-resolve where safe
Configure the scenario’s incomplete-execution settings — auto-retry and resolution strategies for transient errors.
- 3
Fix the root module error
Bulk-completing runs without fixing the module just re-fails them.
- 4
Watch throughput end-to-end
HookShield logs every inbound payload timestamp — a delivery stream that stops matching your execution count is your early warning.
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.