Console
Documentation/Troubleshooting

Troubleshooting

Diagnose connection, delivery and integration failures.

SymptomCheck
UnauthorizedAPI-key value, revocation and selected environment
ForbiddenRequired scope, project/number allowlist and organization membership
Number not readyConnection state, granted assets, registration and permission checks
Message accepted but not deliveredMessage/event timeline and Meta failure details
Duplicate replyConsumer event deduplication and stable send idempotency key
Agent replies to historyProvenance filtering and inbound-only route eligibility
Webhook delivery failsPublic HTTPS, signature configuration, receiver response and delivery attempts
MCP tools work but no inbound automationStart a webhook consumer or event-feed bridge
Missing old conversationsConsent, synchronization deadline, retention and Meta sync limitations
Phone number absentUse business-scoped identity; do not assume every contact exposes E.164

Gather useful diagnostics

Record the request ID, event/message ID, timestamp, connection state and redacted error code. Do not send access tokens, passwords or private message contents to support by default.

Uncertain sends

If the network times out after submission, query the existing message using its idempotency key or returned ID where available. Do not generate a fresh key merely to retry the same business action.

Escalation

Contact [email protected] with redacted diagnostics. Provider approval, Meta account restrictions and application defects require different resolution paths; keep those states distinct in the report.

Prepared 18 November 2026 · Sqkii Pte. Ltd.