Webhook 502 – Upstream Failure Verdict

Verdict (TL;DR)

STOP waiting for retries to fix this.
A 502 indicates upstream instability, not webhook misconfiguration.

Why this happens (structural)

A 502 response is generated by an intermediary or upstream service. Webhook delivery succeeded; processing did not.

Why further debugging often fails

Retrying only re-enters an unstable upstream path. No amount of webhook tuning stabilizes a failing dependency.

Responsibility boundary

Upstream availability is not controlled by the webhook sender. This failure lies outside webhook ownership.

What evidence would change this verdict

• Upstream provider confirms incident resolution
• Verified stable processing independent of webhook retries

Deterministic verification

There is no deterministic webhook-side verification for upstream failures.

Final decision

STOP.
Do not treat this as a webhook problem.