Add WhatsApp delivery error-code reference and re-engagement pattern#10
Draft
posthog[bot] wants to merge 1 commit into
Draft
Add WhatsApp delivery error-code reference and re-engagement pattern#10posthog[bot] wants to merge 1 commit into
posthog[bot] wants to merge 1 commit into
Conversation
The observe-whatsapp playbooks told the agent to "translate error codes into remediation" but shipped no actual mapping, and the only message-debugging example was a happy-path sent->delivered->read timeline. The agent therefore couldn't explain or prevent common WhatsApp delivery failures (notably the 24-hour-window expiry, Meta code 131047). - Add references/delivery-error-codes.md: a Meta delivery error-code -> cause/remediation table (131047, 131026, 131049, 131000 and more) plus a 24-hour-window re-engagement pattern wiring send_template to the whatsapp.message.failed trigger. - Add assets/message-debugging-failed-example.json: a failed-delivery timeline with an error-bearing status entry. - Point the triage and message-debugging playbooks at the new table instead of the vague "map to remediation" instruction; update SKILL.md references and file map. Generated-By: PostHog Code Task-Id: e5d65a7b-ac68-47a7-9045-21339084587a
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The
observe-whatsappskill told the agent to "translate error codes into remediation" / "map to remediation", but shipped no actual error-code mapping, and the only message-debugging example was a happy-pathsent → delivered → readtimeline. As a result the agent couldn't explain or prevent common WhatsApp delivery failures — most notably the 24-hour-window expiry (Meta code131047) — so users fell back to manual UI investigation.references/delivery-error-codes.md— a Meta delivery error-code → cause/remediation table (131047,131026,131049,131000, and more), guidance on where to read the code frommessage.kapso.statuses[].errors[], and a 24-hour-window re-engagement pattern that wires thesend_templatenode to thewhatsapp.message.failedtrigger so the failure can be prevented, not just explained.assets/message-debugging-failed-example.json— a failed-delivery timeline with an error-bearing status entry (131047).SKILL.mdreferences + file map.Why
Recurring session-replay signals showed real users repeatedly hitting and manually investigating WhatsApp delivery failures (including one user hard-blocked mid-reply by the 24-hour window). The skill instructed the agent to map error codes to remediation but shipped no mapping, directly degrading agent diagnosis quality.
Created with PostHog Code from an inbox report.