n8n 1.123.65 - Webhook Stability Fix: Early-Error Promise Resolution

The 1.123.65 maintenance release targets an important integration edge case: webhook execution promises are now settled even when early errors occur. In practice, this prevents hanging or orphaned webhook invocations and ensures upstream callers receive a conclusive response when a webhook fails to process due to early-stage validation or configuration issues.

For businesses that expose webhooks to external partners, or rely on webhooks to trigger backend processes, predictable lifecycle semantics are essential. Hanging requests can lead to longer timeouts, duplicated retries, and resource exhaustion on both client and server sides. By settling promises on early error conditions, n8n reduces the operational burden and makes integrations more resilient and observable.

Technical teams should validate their webhook consumers and orchestrations after applying this patch. Confirm that client-side retry logic and backoff policies behave correctly when the server returns an immediate settled state. Audit any middleware or third-party gateways that might layer their own timeouts or buffering on top of webhook traffic - those components may interact differently with the now-deterministic webhook outcomes.

Recommended actions: (1) deploy the patch to staging and run integration tests with external webhook clients; (2) instrument webhook handlers to ensure early errors are logged and categorized for triage; and (3) review retry policies with API partners to align on expected failure semantics and reduce needless retries.