Quick Answer: This guide lists every known WhatsApp Business Account (WABA) error message you may see in the MyOperator panel or Meta interface and explains, line-by-line, the exact reason and the precise fix you must apply.
1. “Code couldn’t be sent” – Frequent OTP requests
- Error on screen: "Please try again in some time."
- Error Code Details: Code 136024, Type OAuthException, Message "Request code error", Error Subcode 2388091
- Reason: Too many OTP generation attempts for the same number.
- Solution: Wait 24 hours, then try again. If still failing, raise the issue at Meta Direct Support.
2. “Phone number is invalid”
- Error on screen: "Something has gone wrong. You will need to contact support and try again."
- Error Code Details: Code 100, Type OAuthException, Message "Invalid parameter", Error Subcode 2388002
- Reason: IVR for the phone number is not set for direct forwarding.
- Solution: Configure a simple IVR that requires no input and connects callers straight to the client’s number.
3. Template message approval & delivery issues
- Connected WABA & phone number but templates not approved – create the template inside the same, connected WABA and avoid restricted keywords. Test with a very simple template first.
- Templates sent but not delivered – Meta now limits a customer to 5 marketing messages from different companies. If delivery fails, send to 4–5 other numbers. You can also send an incoming message to your own WhatsApp first, then retry the template.
4. Campaign scheduling error “Name already in use”
- Reason: Another campaign already has that name.
- Solution: Give the campaign a unique name and reschedule.
5. Chat page shows “Something went wrong”
- Root cause: Users in a campaign sent unsupported URLs/messages.
- Fix deployed: Unsupported content now appears as an “unsupported message” note; the chat window continues to load normally.
6. “Code couldn’t be sent” – Too many invalid codes
- Error on screen: "You've tried too many invalid verification codes. You'll need to wait a little while before trying again."
- Error Code Details: Code 136024, Type OAuthException, Message "Request code error", Error Subcode 2388091
- Reason: Repeated entry of wrong verification codes.
- Solution: Open a Meta support ticket and request that a Meta agent reset the registration-attempt counter.
7. “Facebook API Failed” – WABA disconnected
- Problem: Error appears when adding a phone number in MyOperator.
- Reason: Client disconnected the WABA from the Facebook Business Manager (FBM) that MyOperator was linked to.
- Solution: Re-onboard – Facebook > WhatsApp > Accounts > Add New Number – then add the phone number again.
8. Maximum phone numbers reached
- Error on screen: "You have already linked the maximum number of phone numbers allowed on this business account. Delete a phone number to continue or request additional numbers."
- Default limit: 2 phone numbers per FBM account.
Solution options:
- Ask Meta (2–3 days) to raise the limit – note: Meta may refuse, the limit cannot always be increased.
- Delete an existing number in FBM, then add the new one.
9. “Facebook API Failed” – General failure
- Reason 1 – Account rejected/blocked: Check status in FBM and contact Meta for reactivation.
- Reason 2 – WABA disconnected from billing: Repeat the full onboarding process from scratch.
10. “Cannot create certificate” – Number registered elsewhere
- Error on screen: "This number is registered to an existing WhatsApp account. To use this number, disconnect it from the existing account."
- If number is in personal WhatsApp/WhatsApp Business App – delete that account first.
- If number is with another BSP – have the BSP remove it from their WABA.
- Wait 4–6 hours after deletion before re-onboarding (Meta processing time).
11. Template rejection after deletion
- Error: "New English content can't be added while the existing English content is being deleted. Try again in 17 days or consider creating a new message template."
- Reason: Meta keeps deleted English templates in “soft-deletion” for 30 days.
- Solution: Create a fresh template with a brand-new name.
The exact formatting guidelines mandated by Meta are:
Use *text* for bold (only single * , never double ** )
Bold each line separately , not the entire block
Keep * tight to text → *Type* ✅, *T *ype ✅, T*ype* ❌
After bullets, add space to make the text bold → - *Body Type: SUV*
Keep headings consistent → *1. ABC* or 1. *ABC*
13. New WABA statuses and panel behavior
You now see real-time WABA status in MyOperator:
- Approved – Meta has approved the account
- Pending – Under Meta review
- Rejected – Not approved
- Unreachable – Billing disconnected or account removed
This helps you instantly understand the account condition without deep checks.
Important behavior changes
- Phone number status remains separate.
- If WABA is “Unreachable”, MyOperator stops fetching webhooks to avoid errors.
- “Sync Now” button still syncs everything and now additionally refreshes WABA status.
- Special scenario: If billing is disconnected or account migrated – WABA status → Unreachable, Phone number status → Deleted or Unreachable. Distinguish both while troubleshooting.
Keywords
WABA, WhatsApp Business Account, OTP error 136024, OAuthException 2388091, invalid phone number 2388002, template approval, marketing message limit, campaign name already in use, chat unsupported message, Facebook API Failed, maximum phone numbers, cannot create certificate, soft deletion 30 days, template bold italics, WABA statuses Approved Pending Rejected Unreachable, MyOperator WhatsApp troubleshooting