A one-customer webhook failure needs a timeline, not just a status code

Webhook debugging note on logging event id, retry timing, status code, timeout, response excerpt, and customer-safe fields.

When a webhook fails for only one customer, a status code alone is rarely enough. The useful support view needs event id, event type, delivery time, retry count, last status, timeout, and a copyable reference the customer can send to their own developer. Internally, the team needs a timeline that separates payload problems, receiver downtime, signature mismatch, rate limiting, and retry exhaustion. Without that timeline, every ticket becomes a manual reconstruction exercise.