Skip to content

docs: help users self-diagnose "Last delivery: Failed" webhooks#13

Draft
posthog[bot] wants to merge 1 commit into
mainfrom
posthog-code/webhook-delivery-failed-troubleshooting
Draft

docs: help users self-diagnose "Last delivery: Failed" webhooks#13
posthog[bot] wants to merge 1 commit into
mainfrom
posthog-code/webhook-delivery-failed-troubleshooting

Conversation

@posthog

@posthog posthog Bot commented Jul 1, 2026

Copy link
Copy Markdown

Why

In a flagged session, a user hit "Last delivery: Failed" on a WhatsApp webhook and kept re-editing event triggers and buffering/debouncing settings trying to fix it — but those settings don't affect delivery success at all. Delivery only fails based on how the receiving endpoint responds. A working diagnostic (webhook-deliveries.js) and a test-delivery flow (test.js) already exist, but the webhook editing docs never pointed to them, so confused users never reached them. This is a repeated-edit pattern seen across many developers.

Changes

  • Add a "Last delivery: Failed" troubleshooting section to webhooks-overview.md and webhooks-reference.md naming the real causes (non-200, timeout, signature mismatch, wrong webhook scope) and making explicit that triggers and buffering don't affect delivery success.
  • Cross-link the webhook editing docs (integrate-whatsapp/SKILL.md) to the webhook-deliveries.js diagnostic (--errors-only/--status) and the test.js test-delivery flow.
  • Note in the Buffering reference that buffering doesn't affect delivery success.

Docs-only change. npm run validate and npm run check:syntax pass.


Created with PostHog Code from an inbox report.

…tic cross-links

Users hitting "Last delivery: Failed" were re-editing event triggers and buffering settings, which cannot affect delivery success — delivery depends only on how the receiving endpoint responds.

- Add a troubleshooting section to webhooks-overview.md and webhooks-reference.md naming the real causes (non-200, timeout, signature mismatch, wrong webhook scope) and stating that triggers/buffering do not affect delivery.
- Cross-link the webhook editing docs (SKILL.md) to the webhook-deliveries.js diagnostic and the test.js test-delivery flow so users diagnose the endpoint instead of tweaking config.
- Note in the Buffering reference that it does not affect delivery success.

Generated-By: PostHog Code
Task-Id: 430f00fb-8e08-4d83-8ad4-3552290c855b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants