Channels (WhatsApp / IG / FB)
About message history on ChatDaddy
ChatDaddy works with WhatsApp to help automate your messages. However, WhatsApp has some limits on how many old messages it can share with us. 1. Message Volume: - Large chat histo…
Updated Apr 15, 2026
Why is my message history not syncing completely?
ChatDaddy works with WhatsApp to help automate your messages. However, WhatsApp has some limits on how many old messages it can share with us.
Key Factors Affecting Sync
- Message Volume:
- Large chat histories can take longer to sync, and some older messages might not be transferred completely.
- WhatsApp's Internal Limits:
- WhatsApp sets specific limits on how much message data can be synced, which affects how complete your message history appears.
How to Access Your Full Message History
To view and search your complete message history, including older messages that may not be synced to ChatDaddy:
- Check Your Primary WhatsApp Device:
-
Your primary phone will always have the most comprehensive and up-to-date message history.
-
WhatsApp's search feature allows you to find specific messages or conversations, even if they haven't fully synced to our product.
We continuously strive to improve our integration with WhatsApp to minimize these limitations. For any specific issues or questions, please reach out to our support team.
Error Glossary
WhatsApp Error Message
| Error Message | Meaning | Possible Cause | Recommended Action | Troubleshooting |
|---|---|---|---|---|
| **"This message is not available" | ||||
| ** | The message cannot be retrieved or displayed. | - Message expired or deleted- Delay in sync or message loading | - Refresh the chat window- Wait briefly and check again- Note: Older messages may not be recoverable if past retention period |
| "Failed to set option" | The system failed to register a button or poll response. | - Recipient did not submit a response- Button or poll expired or removed | - Ask the recipient to respond again- Reissue the button/poll if needed | | | "associatedChildMessage”** ** | Bulk Images with text could not be sent simultaneously | Bulk images with compiled and sent | - Re-upload using a smaller file- Convert the file to a supported format (.mp4, .mov, .avi) | | | "albumMessage"** ** | Bulk images could not be sent simultaneously | Bulk images compiled and sent | Reupload image and send. | | | **“placeholderMessage” ** | a WhatsApp message template includes placeholders (like {{1}}) improperly | A marketing template message cannot be recognized by ChatDaddy | | | | **“pinInMessage“ ** | A message is being pinned by recipient | A trigger happen when recipient pin a message and ChatDaddy tracks the event. | A fix is required to ensure event | | | **“ptvMessage” ** | A Video note send as message | Unsupported format | It will be included as feature request to have this available in the near future. | |
Meta ( Facebook ) Error messages
Authorization Errors
| Error Code | Meaning | Possible Cause | Recommended Action |
|---|---|---|---|
| 401 (0) | Unauthorized – Token expired | The access token used has expired and can no longer be used to authenticate requests. | Get a new access token. |
| 401 (190) | Unauthorized – Token invalidated/revoked | The access token has been invalidated, or the app user has revoked app access via settings. | Get a new access token. |
| 403 (10) | Forbidden – Permission denied | The app does not have the necessary permissions, or permissions have been removed. | Use the Access Token Debugger to verify app permissions. |
| 403 (200-299) | Forbidden – Number not allowlisted | The phone number used to set the business public key is not allowlisted. | Ensure the phone number is allowlisted and tied to your business settings. |
| 404 | Recipient not on WhatsApp | - Phone number is not registered with WhatsApp | - Verify the contact number- Ensure the recipient is using WhatsApp |
| 500 | Internal Server Error | A capability or permission issue occurred on the server side. | Use the Access Token Debugger to verify your app has the required permissions. See Troubleshooting. |
| 551 | Recipient not available | - User has blocked the number- User account may be inactive | - Confirm recipient status- Attempt to reach via another method |
| Integrity Errors |
| Error Code | Meaning | Possible Cause | Recommended Action |
|---|---|---|---|
| 403 (368) | Temporarily blocked for policy violations | The WhatsApp Business Account associated with the app has been restricted or disabled for violating a platform policy. | Refer to the Policy Enforcement documentation to understand and resolve the violation. |
| 403 (130497) | Business account is restricted from messaging users in this country | The WhatsApp Business Account is restricted from messaging users in certain countries. | Refer to the WhatsApp Business Messaging Policy to check allowed countries for your business category. |
| 403 (131031) | Account has been locked | The account has been restricted due to policy violation or because the request data (e.g., two-step PIN) could not be verified against the WhatsApp Business Account. | Review the Policy Enforcement documentation and use the Health Status API for details. |
| Other Errors |
| Error Code | Meaning | Possible Cause | Recommended Action |
|---|---|---|---|
| 400 (1) | API Unknown | Invalid request or possible server error. | Check the WhatsApp Business Platform Status page and verify your request format. |
| 400 (33) | Parameter value is not valid | The business phone number has been deleted. | Verify that the business phone number is correct. |
| 400 (100) | Invalid parameter | Unsupported or misspelled parameters, invalid public key, or mismatched phone ID. | Check parameter spelling and requirements. Verify public key and phone ID. |
| 400 (130472) | User's number is part of experiment | Message was not sent due to experimental restrictions. | Refer to Marketing Message Experiment documentation. |
| 400 (131008) | Required parameter is missing | A required parameter is missing in the request. | Refer to endpoint documentation for required parameters. |
| 400 (131009) | Parameter value is not valid | One or more parameter values are invalid. | Refer to endpoint docs and confirm values. |
| 400 (131021) | Recipient cannot be sender | Sender and recipient phone number are the same. | Use a different recipient number. |
| 400 (131026) | Message Undeliverable | Recipient issues (not on WhatsApp, outdated app, terms not accepted). | Ask recipient to accept T&Cs, update WhatsApp, or verify delivery settings. |
| 400 (131037) | Display name approval needed | Display name not approved for business phone number. | Submit an approved display name per WhatsApp guidelines. |
| 400 (131042) | Business eligibility payment issue | Payment account issues, WABA not linked, or credit problems. | Ensure billing account is active, with currency and timezone set. |
| 400 (131047) | Re-engagement message | 24-hour reply window expired. | Use a pre-approved message template for re-engagement. |
| 400 (131049) | Meta chose not to deliver | Meta prevented delivery to maintain healthy engagement. | Wait and retry using exponential backoff. Review messaging limits. |
| 400 (131050) | User opted out of marketing messages | User has opted out of receiving marketing messages. | Do not retry. Subscribe to user_preferences webhook for updates. |
| 400 (131051) | Unsupported message type | Message type is not supported by WhatsApp. | Refer to supported message types in documentation. |
| 400 (131052) | Media download error | Media could not be downloaded from WhatsApp message. | Ask user to resend media via another method. |
| 400 (131053) | Media upload error | Media file type is unsupported or upload failed. | Inspect MIME type and confirm support. See supported media types. |
| 400 (132000) | Template Param Count Mismatch | Variable count in template doesn't match values sent. | Match the number of variables with the template design. |
| 400 (132005) | Template Hydrated Text Too Long | Translated template text is too long. | Check template translation in WhatsApp Manager. |
| 400 (132007) | Template Format Character Violation | Template content violates a WhatsApp policy. | Review message template rejection reasons. |
| 400 (132012) | Template Parameter Format Mismatch | Variable formatting doesn't match the template. | Ensure values follow required formatting. |
| 400 (132015) | Template is Paused | Template has low quality and is paused. | Edit and improve the template, then resubmit for approval. |
| 400 (132016) | Template is Disabled | Repeated poor quality led to template deactivation. | Create a new, higher-quality template. |
| 400 (132068) | Flow is blocked | Flow is currently blocked. | Correct or reconfigure the Flow. |
| 400 (132069) | Flow is throttled | Message limit reached for the Flow. | Reduce usage or wait before retrying. |
| 400 (133005) | Two-step PIN mismatch | Incorrect two-step verification PIN. | Reset the two-step verification PIN and resend request. |
| 400 (133006) | Re-verification needed | Phone number must be verified before registration. | Verify the phone number before proceeding. |
| 400 (133008) | Too many PIN guesses | Excessive incorrect attempts. | Wait as instructed in the error response. |
| 400 (133009) | PIN guesses too fast | PINs were guessed too quickly. | Delay and try again. |
| 400 (133010) | Phone not registered | The number isn't yet registered with WhatsApp Business Platform. | Register the phone number. |
| 400 (133015) | Wait before re-registering | Number was recently deleted and is not ready to re-register. | Wait 5 minutes before retrying. |
| 400 (134011) | Payments TOS not accepted | Payments terms of service not accepted. | Accept the terms using the link in the error message. |
| 400 (135000) | Generic user error | Unknown parameter error. | Refer to How to Fix the Generic User Error (135000) in WhatsApp Cloud API** **documentation. |
| 403 (131005) | Access Denied | Permissions missing or revoked. | Use token debugger to verify granted permissions. |
| 404 (132001) | Template not found | Template not approved or not available in specified language. | Ensure correct name, locale, and approval. |
| 500 (131000) | Something went wrong | Unknown send error, signature, or GraphQL issue. | Retry. If persistent, open a Direct Support ticket. |
| 500 (131016) | Service unavailable | A backend service is temporarily unavailable. | Check platform status and retry. |
| 500 (131045) | Incorrect certificate | Registration-related certificate error. | Register the phone number again. |
| 500 (131057) | Account in maintenance | Account is undergoing upgrades or maintenance. | Wait until maintenance completes. |
| 500 (133000) | Incomplete deregistration | Prior deregistration failed. | Retry deregistration before registering. |
| 503 (2) | API Service | Temporary downtime or service overloaded. | Check platform status and try again later. |
| 503 (133004) | Server temporarily unavailable | Server is down or overloaded. | Check status and response details before retrying. |
| Error Code | Meaning | Possible Cause | Recommended Action |
| --- | --- | --- | --- |
| 400 (4) | API Too Many Calls | The app has reached its API call rate limit. | Check the App Dashboard > Application Rate Limit. Retry later or reduce the frequency of API requests. |
| 400 (80007) | Rate limit issues | The WhatsApp Business Account has reached its rate limit. | See WhatsApp Business Account Rate Limits. Retry later or reduce API query frequency. |
| 400 (130429) | Rate limit hit | Cloud API message throughput has been reached. | See Throughput documentation. Retry later or slow down message sending rate. |
| 400 (131048) | Spam rate limit hit | Too many messages were blocked or flagged as spam, triggering restrictions on sending messages. | Check the quality rating in WhatsApp Manager. Review Quality-Based Rate Limits. |
| 400 (131056) | (Business, Consumer) pair limit hit | Too many messages sent from one business phone number to the same user in a short time. | Wait before retrying to the same number. You may continue sending to other numbers. |
| 400 (133016) | Register/Deregister rate limit hit | Too many registration/deregistration attempts for the same phone number in a short time. | Wait until the number is unblocked before retrying. See “Limitations” in Registration documentation. |
Feedback
Was this article helpful?