X_WEBHOOK_ENDPOINT_DISABLED

the endpoint takes no deliveries

the app disabled the row — refused before the ledger and before the socket, which is the whole point of disabling one — or this delivery is the one that reached disableAfter (default 10 consecutive failures, roughly a day of a retrying queue against a dead receiver), where cause prints both numbers. In the second case this code REPLACES the attempt's own: what an operator needs to see is that deliveries have stopped, not the status of the one that tipped it over. Terminal by construction — the next attempt reads the same row

fix the receiver, then re-enable the endpoint in your own table and enqueue the deliveries it missed — the framework never re-enables one on its own, because a dead endpoint that heals itself is a retry loop with no end