Meta Errors in BotPenguin
This page contains a comprehensive guide on all the common errors of Meta on BotPenguin
What are Meta Errors?
Meta errors occur when BotPenguin is unable to complete an action involving WhatsApp, Instagram, or Facebook integrations.
These actions include:
Connecting your Meta accounts
Sending messages or broadcasts
Submitting WhatsApp templates
Uploading media
Running automations (drips, chat flows)
Since BotPenguin relies on Meta APIs, any issue from Meta’s side or setup can result in an error.
Why do these errors happen?
Meta errors typically occur due to:
Missing permissions or access rights
Expired or invalid login sessions
Incorrect configuration of accounts or assets
Messaging restrictions (like 24-hour window rules)
Template or policy violations
Rate limits or system overload
Media format or size issues
Common Meta Errors & How to Fix Them
Meta Error Code: OAuthException — Authorization Cancelled
What this means
The Meta authorization flow was started, but it was not completed successfully.
This usually happens before the channel is connected, so BotPenguin cannot proceed with onboarding.
Why this happens
This error commonly appears when:
you close the Meta login or authorization window manually
you click Cancel or deny access on a Meta permissions screen
the login session expires before the setup is completed
the onboarding flow is left idle for too long
How to fix this
Follow these steps:
Go back to the BotPenguin channel connection screen.
Start the Meta onboarding process again.
Complete the Facebook login flow using the correct account.
When Meta asks for permissions, click Allow or Continue on each step.
Stay on the setup screen until the process fully completes and redirects back to BotPenguin.
What to check before trying again
Make sure you are using the correct Facebook account.
Do not close the Meta window during setup.
Complete the flow in one attempt without leaving it idle.
Meta Error Code: OAuthException — Popup Blocked / Setup Interrupted
What this means
The Meta onboarding window could not complete properly because the setup flow was interrupted.
BotPenguin depends on the Meta popup window to complete authorization. If that window is blocked or interrupted, the connection cannot finish.
Why this happens
This usually happens when:
your browser blocks popups
a browser extension or ad blocker interferes with the Meta login flow
the Meta popup opens but closes unexpectedly
the browser session times out during onboarding
network instability interrupts the setup process
How to fix this
Try the following steps in order:
Enable popups for BotPenguin in your browser settings.
Temporarily disable ad blockers, privacy blockers, or script-blocking extensions.
Refresh the BotPenguin page.
Start the onboarding flow again.
Complete the Meta setup in the same browser tab without switching devices or browsers midway.
What to check before trying again
Use a supported browser such as Chrome.
Ensure your internet connection is stable.
Avoid opening multiple Meta onboarding windows at the same time.
Meta Error Code: 190 — Access Token Expired or Connection Revoked
What this means
Your Meta connection is no longer valid because the access token has expired or the connection has been revoked.
Since BotPenguin uses this token to access your Meta assets, the action cannot continue until the connection is refreshed.
Why this happens
This can happen when:
the Meta session has expired
the connected account was disconnected from Meta
permissions were removed after the initial connection
the Facebook account password or security settings were changed
the connection has not been refreshed for a long time
How to fix this
Use the following steps:
Go to the relevant channel integration inside BotPenguin.
Disconnect the current Meta connection if needed.
Start the connection process again.
Log in with the correct Meta account.
Grant all required permissions again.
Retry the action after reconnection.
What to check before trying again
Make sure the correct Meta account is being used.
Confirm that the account still has access to the connected assets.
Check whether the connection was removed or permissions were changed recently.
Meta Error Code: 102 — Session Invalid
What this means
Your current Meta login session is no longer valid, so BotPenguin cannot complete the request.
This usually affects onboarding or any action that depends on an active Meta session.
Why this happens
This can happen when:
your Facebook login session has expired
you were logged out in another browser or device
the session timed out during setup
the browser stored an outdated or broken session state
How to fix this
Use the following steps:
Log out of Facebook if you are currently signed in.
Close the affected browser tab.
Open BotPenguin again and restart the Meta flow.
Log back in to Facebook using the correct account.
Complete the required action again.
What to check before trying again
Make sure you are not using an expired browser session.
Avoid keeping the Meta flow open for too long.
Use one browser session for the full setup.
Meta Error Code: 200 — Permission Denied / Missing Access
What this means
BotPenguin reached Meta successfully, but Meta denied access to the selected business asset.
This usually means the logged-in Facebook account does not have the required permissions for the selected Business Manager, Facebook Page, Instagram account, or WhatsApp Business Account.
Why this happens
This can happen when:
you are not an admin of the selected Business Manager
you do not have permission to access the selected Page or account
the asset belongs to another business
the required permissions were not granted during setup
access was removed after the channel was connected
How to fix this
Use the following steps:
Confirm which Facebook account is currently logged in.
Check whether that account has admin access to the required Meta assets.
Open Meta Business Manager and verify your role.
Restart the BotPenguin integration flow.
Approve all requested permissions when Meta asks.
Re-select the correct assets during setup.
What to check before trying again
You should have admin access to the Business Manager.
You should also have access to the selected Page, Instagram account, or WhatsApp Business Account.
Make sure the correct Meta account is being used.
Meta Error Code: 10 — App Missing Required Permissions
What this means
The requested action cannot be completed because the required Meta permissions were not granted to BotPenguin.
Why this happens
This can happen when:
one or more permission screens were skipped or denied
the app authorization was only partially completed
permissions were later removed from Meta
the current account does not allow the requested scope
How to fix this
Use the following steps:
Go to the channel integration in BotPenguin.
Reconnect the Meta account from scratch.
Review all permission prompts carefully.
Approve every required permission.
Retry the action after the connection is completed again.
What to check before trying again
Make sure no permission prompt is denied.
Use an account with authority to grant permissions.
Check whether the integration was previously connected with partial access only.
Meta Error Code: 33 — Asset Not Found / Not Accessible
What this means
The selected Meta asset could not be found or could not be accessed.
Depending on the flow, this could refer to a Facebook Page, Instagram account, WhatsApp account, phone number, or another Meta-linked object.
Why this happens
This can happen when:
the selected asset no longer exists
the asset belongs to another business
your account does not have access to it
the wrong asset was selected
the asset was removed, unlinked, or renamed
How to fix this
Use the following steps:
Open Meta Business Manager and locate the asset.
Confirm that the asset still exists and is active.
Check that the asset belongs to the expected business.
Verify that your account has access to it.
Return to BotPenguin and restart the flow.
Re-select the correct asset.
What to check before trying again
The asset should exist and be visible in Meta.
It should be linked to the correct business.
Your account should have permission to manage it.
Meta Error Code: 100 — Invalid Request / Missing Required Input
What this means
The request sent to Meta is incomplete, invalid, or not accepted in its current form.
Why this happens
This can happen when:
a required field is missing
an unsupported value was sent
the selected setup step was not completed properly
the wrong object type was used for the action
the request was triggered with incomplete configuration
How to fix this
Use the following steps:
Review all the inputs or configuration used for the action.
Make sure required fields are filled correctly.
Confirm that the correct business asset is selected.
Retry the action after correcting the missing or invalid value.
If this happens during onboarding, restart the flow and complete each step carefully.
What to check before trying again
No required field should be blank.
The selected account or asset should match the intended action.
Avoid switching between assets midway through setup.
Meta Error Code: 2635 — Business Verification Required
What this means
Meta requires business verification before allowing the requested feature or action.
Until verification is complete, BotPenguin cannot proceed with the restricted Meta functionality.
Why this happens
This can happen when:
The business is not yet verified in Meta Business Manager
Verification is incomplete or pending review
The requested feature requires a verified business
Submitted business documents were rejected or not approved yet
How to fix this
Use the following steps:
Open Meta Business Manager.
Go to the business verification section.
Complete all required business verification steps.
Submit the necessary documents if required.
Wait until Meta marks the business as verified.
Retry the action in BotPenguin.
What to check before trying again
Confirm whether verification is required for the feature you are using.
Make sure your documents are valid and complete.
Check whether verification is pending or rejected.
Meta Error Code: 368 — Action Temporarily Blocked
What this means
Meta has temporarily restricted the requested action due to account or policy-related limitations.
Why this happens
This can happen when:
Meta detects suspicious or restricted activity
the business has violated a Meta policy
repeated actions triggered a temporary safeguard
the account is under review or partially restricted
How to fix this
Use the following steps:
Open your Meta account status or Business Manager.
Review any warnings, restrictions, or policy notices.
Resolve the flagged issue if one is shown.
Wait for the temporary restriction period to pass.
Retry the action only after the account status is clear.
What to check before trying again
Check for policy warnings in Meta.
Avoid retrying the same blocked action repeatedly.
Make sure the account is in good standing.
Meta Error Code: 4 — Application Rate Limit Reached
What this means
Too many requests were sent from the application to Meta in a short period of time.
Why this happens
This can happen when:
a large number of API actions were triggered together
repeated retries were attempted too quickly
multiple users or automations are hitting the same integration at once
How to fix this
Use the following steps:
Stop retrying the action immediately.
Wait for a short period.
Retry the action after a few minutes.
Reduce repeated bulk actions if possible.
What to check before trying again
Check whether broadcasts, drips, or automations are firing in bulk.
Avoid repeated manual retries in a short span.
Retry only after allowing cooldown time.
Meta Error Code: 17 — User Rate Limit Reached
What this means
The Meta account used for the action has reached its current request limit.
Why this happens
This can happen when:
too many actions were triggered from the same account
repeated asset management or messaging actions were performed
the account is temporarily throttled by Meta
How to fix this
Use the following steps:
Pause further actions from the affected account.
Wait for the limit window to reset.
Retry the action later.
Reduce repeated actions from the same account where possible.
What to check before trying again
Do not perform repeated retries from the same account.
Check whether the same account is being used across multiple flows.
Allow some time before reattempting.
Meta Error Code: 613 — API Request Frequency Exceeded
What this means
The frequency of requests sent to Meta exceeded the allowed threshold.
Why this happens
This can happen when:
automated requests are firing too frequently
the same action is being retried repeatedly
multiple systems are calling the same Meta asset quickly
How to fix this
Use the following steps:
Pause the repeated action.
Wait before sending the next request.
Retry after a cooldown period.
Reduce excessive retry behaviour in the workflow.
What to check before trying again
Make sure automations are not looping.
Check whether retry behaviour is too aggressive.
Avoid high-frequency back-to-back requests.
Meta Error Code: 80008 — Too Many Requests to WhatsApp Business Account
What this means
Too many API or messaging-related requests were sent to the connected WhatsApp Business Account in a short time.
Why this happens
This can happen when:
bulk broadcasts are triggered together
repeated message retries happen too fast
multiple workflows use the same WhatsApp account simultaneously
the account is being throttled by Meta
How to fix this
Use the following steps:
Stop retrying the request immediately.
Wait for a short cooldown period.
Retry after some time.
Spread out bulk actions if possible.
Check whether another workflow is using the same WhatsApp account heavily.
What to check before trying again
Avoid sending large volumes at once.
Check for duplicate automations or repeat triggers.
Make sure the same number is not being overused across workflows.
Meta Error Code: 131030 — Phone Number Not Registered
What this means
The phone number is not registered for WhatsApp Business API usage.
Why this happens
This can happen when:
the number was never fully onboarded in Meta
the number is not properly set up for WhatsApp Business API
the wrong number was selected during configuration
How to fix this
Use the following steps:
Open the WhatsApp setup in Meta Business Manager.
Confirm whether the number has been registered successfully.
If not, complete the number registration process.
Return to BotPenguin and retry the setup.
What to check before trying again
Make sure the correct phone number is being used.
Confirm that the number is active in the intended WhatsApp Business Account.
Check that the registration process completed successfully.
Meta Error Code: 131037 — Phone Number Already Registered Elsewhere
What this means
The phone number you are trying to use is already connected to another WhatsApp setup.
Why this happens
This can happen when:
the number is already linked to another WhatsApp Business Account
the number is still active in another WhatsApp configuration
the same number was previously onboarded elsewhere and not released properly
How to fix this
Use the following steps:
Identify where the number is currently connected.
Remove or disconnect the number from the existing setup if it is no longer needed there.
Wait for the number to be released if Meta requires time for that update.
Start onboarding again in BotPenguin using the same number only after it is fully free.
If the number cannot be released, use a different number.
What to check before trying again
The number should not already be attached to another active WhatsApp setup.
Check both WhatsApp app usage and WhatsApp Business platform usage.
Confirm with your team that the number is not already in use elsewhere.
Meta Error Code: 131042 — Business eligibility / payment issue
What this means
The message could not be sent because your WhatsApp Business account has a billing or eligibility issue.
Why this happens
payment method missing
billing account issue
credit limit reached
business not eligible
How to fix
go to Meta Business Manager → Billing
add/update payment method
clear dues
ensure account is active
What to check before trying again
Your Meta Business account should have an active and valid payment method.
There should be no outstanding dues or failed payments in your billing account.
Your WhatsApp Business Account should be active and not restricted.
Check that your business is eligible and verified for WhatsApp usage in Meta Business Manager.
Ensure your billing account is linked correctly to the WhatsApp Business Account.
Avoid retrying immediately until the billing or eligibility issue is resolved.
Meta Error Code: 131048 — Phone Number Not Linked to WhatsApp Business Account
What this means
The phone number exists, but it is not linked correctly to the selected WhatsApp Business Account.
Why this happens
This can happen when:
the number belongs to a different WhatsApp Business Account
the number was added but not linked properly
the wrong WABA was selected in the flow
How to fix this
Use the following steps:
Open Meta Business Manager.
Go to the selected WhatsApp Business Account.
Confirm whether the phone number is linked there.
If not, link the correct phone number to the correct WABA.
Return to BotPenguin and retry the action.
What to check before trying again
The number and WABA should belong to the same setup.
Confirm the right WABA is selected.
Avoid mixing phone numbers across businesses.
Meta Error Code: 131045 — Phone Number Messaging Limit Reached
What this means
The connected WhatsApp number has reached its current messaging limit.
Why this happens
This can happen when:
the number has hit Meta’s current messaging capacity
the account quality has affected throughput
too many messages were attempted within the active limit
How to fix this
Use the following steps:
Pause new outbound message attempts temporarily.
Wait until the messaging limit resets or capacity becomes available again.
Review message quality and delivery performance in Meta if available.
Retry sending later.
What to check before trying again
Avoid sending large outbound volumes at once.
Check whether the number has quality or tier limitations.
Make sure retries are not inflating the load.
Meta Error Code: 131026 — Message Delivery Failed
What this means
The message could not be delivered to the recipient.
This is a delivery-level failure from Meta, meaning the message request was processed but could not reach the user successfully.
Why this happens
This can happen when:
the recipient’s phone number is invalid or incorrectly formatted
the number is not registered on WhatsApp
the user is temporarily unavailable or inactive
there is a temporary delivery issue on Meta’s side
the message could not be routed properly
How to fix this
Use the following steps:
Verify the recipient’s phone number, including country code.
Confirm that the number is registered on WhatsApp.
Retry sending the message after some time.
If possible, ask the user to initiate the conversation again.
Avoid repeated retries in a short period.
What to check before trying again
The phone number should be valid and correctly formatted.
The recipient should be an active WhatsApp user.
The issue should not be caused by temporary delivery disruption.
Do not retry immediately multiple times.
Meta Error Code: 131047 — Message Sent Outside 24-Hour Window
What this means
A free-form WhatsApp message was attempted outside the allowed customer service window.
WhatsApp only allows free-form replies within 24 hours of the user’s last message. Outside that window, an approved template message is required.
Why this happens
This can happen when:
the user has not messaged within the last 24 hours
a broadcast, drip, or manual message was sent as a regular message instead of a template
the workflow is using the wrong message type
How to fix this
Use the following steps:
Check when the user last interacted with the business.
If the 24-hour window has expired, do not send a free-form message.
Use an approved WhatsApp template instead.
If applicable, wait for the user to message again before sending a free-form reply.
What to check before trying again
Confirm whether the message is inside or outside the 24-hour window.
Use templates for outbound re-engagement.
Make sure automations are configured with the correct message type.
Meta Error Code: 131049 — User Blocked the Business
What this means
The recipient is not currently available for messaging from the connected business account.
In many cases, this means the user has blocked the business or is otherwise unavailable for delivery.
Why this happens
This can happen when:
the user blocked the business number
the recipient is not reachable for messaging
delivery is restricted on the recipient side
How to fix this
Use the following steps:
Stop retrying the same message repeatedly.
Wait to see if the user re-engages later.
If the user contacts the business again, retry communication at that point.
What to check before trying again
Do not keep retrying messages to the same blocked recipient.
Wait for the recipient to reinitiate contact where possible.
Make sure the number is correct before assuming a block-related issue.
Meta Error Code: 131051 — Unsupported Message Type
What this means
The message type or payload used for the WhatsApp action is not supported.
Why this happens
This can happen when:
the chosen message format is not supported by the account
the payload structure does not match Meta’s allowed format
an unsupported content type is being used in the flow
How to fix this
Use the following steps:
Review the type of message being sent.
Confirm that the selected message format is supported by WhatsApp.
Check whether the message content is configured correctly.
Replace the unsupported type with a supported one.
Retry the action.
What to check before trying again
Make sure the message format is supported for the channel and use case.
Check whether the payload structure is valid.
Avoid mixing unsupported content types in one request.
Meta Error Code: 131000 — Generic WhatsApp API Error
What this means
Meta could not complete the WhatsApp request due to an unspecified or unexpected API issue.
Why this happens
This can happen when:
Meta returned a generic backend failure
the issue does not match a more specific error category
there is a temporary internal problem in the WhatsApp API flow
How to fix this
Use the following steps:
Retry the action once after a short wait.
If the error happens during setup, refresh the flow and try again.
If the error happens repeatedly, stop retrying continuously.
Contact support with the exact action and screenshot if the issue persists.
What to check before trying again
Confirm whether the issue is temporary or recurring.
Check whether other Meta actions are also failing.
Avoid repeated retries in a very short time.
Meta Error Code: 132000 — Template Variable Mismatch
What this means
The values passed into the WhatsApp template do not match the approved template structure.
Why this happens
This can happen when:
the number of variables does not match the approved template
the variables are passed in the wrong order
a required variable is missing
the message structure differs from the approved template format
How to fix this
Use the following steps:
Open the template configuration in BotPenguin.
Check the approved template structure in Meta.
Confirm how many variables are expected.
Make sure each variable is mapped in the correct order.
Remove extra variables and fill any missing ones.
Retry the message.
What to check before trying again
The variable count should match exactly.
Variable order should match the approved template.
No required placeholder should be left empty.
Meta Error Code: 132001 — Template Not Found
What this means
The selected WhatsApp template could not be found by Meta.
Why this happens
This can happen when:
the template does not exist in the connected Meta account
the template name is incorrect
the template belongs to another WABA
the template was deleted or is unavailable
How to fix this
Use the following steps:
Open the template list in Meta or BotPenguin.
Confirm that the template exists and is active.
Make sure the correct template is selected.
Verify that the template belongs to the connected WhatsApp Business Account.
Retry the message using the correct template.
What to check before trying again
The template name should match exactly.
The template should belong to the correct account.
The template should still be available and approved.
Meta Error Code: 132005 — Template Content Too Long or Invalid
What this means
The template content or variable-filled content exceeds Meta’s allowed format or length requirements.
Why this happens
This can happen when:
variable values make the final message too long
invalid content is inserted into a template field
How to fix this
Use the following steps:
Review the content being passed into the template.
Shorten long variable values where possible.
Remove unnecessary text or formatting.
Retry with a shorter final message output.
What to check before trying again
Check the final message after variables are filled.
Make sure content stays within allowed length.
Avoid very long dynamic values in placeholders.
Meta Error Code: 132007 — Template Policy Violation
What this means
The template does not comply with WhatsApp’s policy or formatting requirements.
Why this happens
This can happen when:
the content violates WhatsApp template guidelines
the template contains restricted or non-compliant wording
the format does not meet Meta approval requirements
How to fix this
Use the following steps:
Review the rejected or problematic template content.
Compare it against WhatsApp template guidelines.
Remove policy-sensitive or non-compliant wording.
Update the template content.
Resubmit the template for approval.
What to check before trying again
Make sure the template is clearly transactional or appropriately categorized.
Avoid promotional or misleading wording where not allowed.
Follow Meta’s current template formatting rules.
Meta Error Code: 132012 — Template Paused by Meta
What this means
The selected template is currently paused and cannot be used for sending.
Why this happens
This can happen when:
Meta paused the template due to quality or policy reasons
the template is temporarily unavailable
the template status changed after it was previously approved
How to fix this
Use the following steps:
Check the template status in Meta.
Confirm whether the template is paused or disabled.
Use another approved template if immediate sending is required.
If allowed, update or reactivate the template in Meta.
Retry only with an active template.
What to check before trying again
The template should be active and approved.
Do not retry using a paused template.
Keep a fallback approved template available if possible.
Meta Error Code: 131052 — Media Upload Failure
What this means
The media file could not be uploaded or processed successfully by Meta.
Why this happens
This can happen when:
the upload was interrupted
the file is corrupted
there was a temporary network issue
Meta could not process the file correctly
How to fix this
Use the following steps:
Retry the upload once.
Check your internet connection.
Confirm that the file opens correctly on your device.
Re-upload the file.
If the issue continues, try a fresh copy of the file.
What to check before trying again
The file should not be corrupted.
Your internet connection should be stable.
The file should be in a supported format and size range.
Meta Error Code: 131053 — Unsupported Media Format
What this means
The uploaded media type is not supported by Meta for the requested action.
Why this happens
This can happen when:
the file format is not supported
the file extension does not match the actual media type
the content type is invalid for the selected channel or message type
How to fix this
Use the following steps:
Check the file format you are trying to upload.
Convert the file into a supported format if needed.
Re-upload the file using a supported media type.
Retry the action.
What to check before trying again
Make sure the file is in a supported format such as the allowed image, video, or document type.
Avoid renamed files with mismatched extensions.
Confirm the media type is valid for the chosen use case.
Meta Error Code: 131054 — File Size Exceeds Limit
What this means
The uploaded media file is larger than Meta’s allowed file size limit.
Why this happens
This can happen when:
the image, video, or document is too large
the exported file contains unnecessary high resolution or metadata
the file exceeds the size allowed for that media category
How to fix this
Use the following steps:
Check the file size before uploading.
Compress or resize the file.
Reduce video resolution or image quality if needed.
Upload the smaller version again.
What to check before trying again
The file size should be within Meta’s supported limits.
Large videos and documents should be compressed before upload.
Keep optimized media versions ready for reuse.
Meta Error Code: 131055 — Media Retrieval Failure
What this means
Meta could not retrieve or access the uploaded media file successfully.
Why this happens
This can happen when:
the media file became unavailable
the upload did not complete properly
the file could not be fetched from Meta servers
the media reference is stale or broken
How to fix this
Use the following steps:
Remove the failed media from the current flow.
Upload the media file again from a fresh source.
Retry the action after the new upload completes.
If the error repeats, use a freshly exported copy of the file.
What to check before trying again
Make sure the media was uploaded completely.
Avoid using broken or outdated media references.
Confirm the file is still accessible and valid.
Meta Error Code: Any — Unknown or Unmapped Error
What this means
Meta returned an error that does not currently match a specific mapped category in BotPenguin.
Why this happens
This can happen when:
Meta introduced a new error code
the issue is unexpected or uncommon
the response did not match a standard error mapping
How to fix this
Use the following steps:
Retry the action once after a short wait.
Check whether the issue is temporary.
Capture a screenshot of the error message.
Note what action you were trying to perform.
Contact support if the issue continues.
What to check before trying again
Confirm whether the same issue happens repeatedly.
Check whether it affects only one action or multiple actions.
Be ready to share the exact workflow and screenshot for faster support.
Still Need Help?
If you have followed all the steps above and are still unable to resolve the issue, please reach out to our support team.
Write to us at support@botpenguin.com with the following details:
Screenshot of the error
Meta error code (if visible)
Action you were trying to perform
Connected channel (WhatsApp / Instagram / Facebook)
We will respond within 48 business hours.
Frequently Asked Questions (FAQs)
1. Why does my Meta connection keep disconnecting?
This usually happens when:
your Meta access token expires
permissions are revoked
your Facebook password or security settings change
Reconnecting your Meta account will usually fix this.
2. I have admin access but still see a permission error. Why?
This can happen if:
you are admin of the Page but not the Business Manager
the asset belongs to a different business
permissions were not approved during onboarding
Make sure you have access to both Business Manager and the asset.
3. Why can I see my Page in Meta but not in BotPenguin?
This usually means:
the Page is not linked to the selected Business Manager
you don’t have the required role for that Page
you selected a different business during onboarding
Reconnect and carefully select the correct Business.
4. Why is my WhatsApp number getting rejected during setup?
Common reasons include:
the number is already registered in another WhatsApp setup
it is still active on WhatsApp Business App
it was not properly removed from a previous provider
You may need to fully release the number or use a new one.
5. Why am I unable to send messages even though setup is complete?
This can happen due to:
the 24-hour messaging window restriction
messaging limits on your number
user blocking your business
template-related issues
Check the exact error code for the root cause.
6. Why do my WhatsApp templates keep failing?
Templates can fail due to:
variable mismatch
policy violations
incorrect formatting
excessive length
Always match the exact approved template structure.
7. Why does my broadcast or drip fail midway?
This usually happens due to:
rate limits being hit
invalid recipients
template issues
temporary Meta API failures
Wait and retry after some time, and check logs for failed users.
8. Why am I seeing rate limit errors frequently?
This happens when:
too many messages or API calls are triggered quickly
multiple automations run at the same time
repeated retries are made
Try spacing out actions and avoid rapid retries.
9. Can I retry immediately after an error?
Not always.
For rate limit errors → wait before retrying
For permission or setup errors → fix the issue first
For temporary errors → retry once after a short delay
10. Why does media upload fail even when the file looks fine?
Possible reasons:
file format not supported
file size too large
file is corrupted
upload interrupted
Try re-uploading a fresh, compressed version of the file.
11. Why does the same action work for some users but fail for others?
This is usually due to:
recipient-side issues (blocked, inactive, unreachable)
different messaging windows
partial data issues
template personalization differences
12. What happens if I keep retrying the same failed action?
Repeated retries can:
trigger rate limits
worsen temporary restrictions
delay resolution
It’s better to identify the root cause first before retrying.
13. Do Meta errors always mean something is wrong on BotPenguin?
No. Most Meta errors originate from:
Meta platform rules
account configuration
permission issues
API limits
BotPenguin simply surfaces these errors with guidance.
14. How do I know if the issue is from Meta or BotPenguin?
If the error:
mentions permissions, templates, or limits → likely Meta
occurs during API actions → likely Meta
occurs across multiple actions consistently → could be integration
When in doubt, share details with support.
15. Can switching accounts fix Meta errors?
Yes, in many cases.
Using the correct account with:
proper permissions
correct business access
valid assets
can resolve onboarding and permission-related errors.
16. Why does everything work on web but not on mobile (or vice versa)?
Possible reasons:
session mismatch
outdated login
cached data issues
different account logged in
Try re-login and sync both platforms.
17. Will deleting and reconnecting the integration help?
Yes, especially for:
token expiry issues
permission issues
incorrect asset mapping
But ensure you reconnect with the correct setup and permissions.
18. What should I do before contacting support?
Before reaching out, make sure you:
retry after checking the fix steps
note the exact error code
capture a screenshot
confirm your account and asset setup
This helps resolve your issue faster.
Last updated