docs: consolidate WhatsApp template rejection troubleshooting#14
Draft
posthog[bot] wants to merge 1 commit into
Draft
docs: consolidate WhatsApp template rejection troubleshooting#14posthog[bot] wants to merge 1 commit into
posthog[bot] wants to merge 1 commit into
Conversation
Users hit Bad Request errors when creating WhatsApp templates and had to piece together the cause from scattered rules across templates-reference.md and the WhatsApp SKILL files. Add a single "Troubleshooting: why did my template get rejected?" section to templates-reference.md that maps each Meta failure to a plain-English cause and fix: example/variable mismatches and positional gaps that produce a Bad Request, category restrictions (MARKETING vs UTILITY vs AUTHENTICATION), and the Meta business verification requirement tied to OAuthException 139000. Surface it from observe-whatsapp's triage reference and cross-link from both skills so a human or the support chatbot can self-serve. Generated-By: PostHog Code Task-Id: 85975335-f067-4dd5-ac5a-470f31a82d6b
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
Users setting up outbound WhatsApp messaging kept hitting Bad Request errors when creating templates and had no single place to figure out why — the relevant rules (example/variable requirements, the three categories, and the business-verification requirement) were scattered across
templates-reference.mdand the WhatsAppSKILL.mdfiles, with the OAuthException 139000 note buried under Flows troubleshooting.This adds a focused "Troubleshooting: why did my template get rejected?" section to
templates-reference.mdthat maps each Meta failure to a plain-English cause and fix:(#100)) at creation — the common example/variable mismatches: missing example per variable, example keys not matchingparameter_format(NAMED vs POSITIONAL),param_namenot matching the placeholder, positional gaps, count mismatch, and flat-vs-2Dbody_text.It's surfaced from
observe-whatsapp(new "Template creation rejected" entry intriage-reference.mdplus a pointer in itsSKILL.md) and cross-linked fromintegrate-whatsapp, so both a human and the Agente Kapso chatbot can self-serve instead of guessing.Why
Two independent session recordings a week apart showed users stuck in the template-creation flow — one blocked by a Bad Request, the other spending real time bouncing between the new-template form and verification pages before falling back to the support chatbot. Template creation is a core integration flow, and the fix is a documentation consolidation of knowledge that already exists in the repo.
Created with PostHog Code from an inbox report.