Quick Answer

This guide lists every known WhatsApp Business Account (WABA) error code, failure reason, and the exact corrective action you should take inside the MyOperator panel or in Meta Business Manager.

1. OTP & Verification Problems

The error “Code couldn’t be sent” with code 136024 / sub-code 2388091 appears in two distinct situations:

• You requested an OTP too frequently. You must wait exactly 24 hours before the next attempt, then raise a ticket at https://business.facebook.com/direct-support/ if the lockout persists.
• You entered the wrong OTP repeatedly. Meta blocks further tries; only a Meta support agent can reset the counter once you file a ticket at the same Direct Support URL.

During onboarding, follow these rules to avoid OTP failures:

1. The Automated OTP Mode for MyOperator virtual numbers runs a 5-minute active timer; keep the tab open and do not refresh.
2. If an OTP fails, the system enforces a 15-minute cooldown before another request will work.
3. Never exceed three OTP requests for any number within 24 hours—doing so triggers a mandatory 24-hour lockout.
4. Solely use a standard 10-digit mobile, landline, or virtual number; toll-free (1800) numbers are technically barred from WhatsApp Business API registration.
5. With client-owned numbers, switch between SMS and Voice Call after waiting at least 45 seconds, and verify that the IVR call flow forwards instantly with no DTMF input.

2. Phone Number & Certificate Errors

“Phone number is invalid” (code 100 / sub-code 2388002) means the IVR tree is too complex. Rebuild the flow so the call connects straight to the handset without any key presses.

“Cannot create certificate – This number is registered to an existing WhatsApp account” shows the number is live elsewhere. Delete the personal WhatsApp or ask the current BSP to remove the number, wait 4-6 hours for Meta to purge the record, and then re-onboard in MyOperator.

If you see “Maximum phone numbers reached”, the Facebook Business Manager (FBM) owns a hard limit of two numbers by default. Raise a Direct Support ticket to increase the quota (Meta’s response time is typically 2-3 days) or simply delete a spare number before adding a new one.

3. Template Creation, Approval & Formatting

Templates fail to approve when they are created under the wrong WABA, contain restricted keywords, or reuse a deleted-template name that is still in Meta’s 30-day soft-deletion window. Always build the template in the connected WABA, use a brand-safe phrase set, and choose an unused template name if Meta states “Try again in 17 days”.

Formatting rules for bold and italics must be followed exactly; copy the official guidance below:

Use text for bold (only single *, never double **)
Bold each line separately, not the entire block
Keep * tight to text → Type ✅ , T ype ❌ , Type ❌
After bullets, add space to make the text bold → - Body Type: SUV
Keep headings consistent → 1. ABC or 1. ABC

4. Message Delivery Failures & Error Codes 131049 / 131026

Undelivered WhatsApp template or campaign messages fall into five precise buckets:

• 131049 – Meta Marketing Frequency Cap: A user can receive only three to five marketing messages per day across all businesses. Once capped, Meta returns “Healthy Ecosystem Limit Reached”.
• 131026 – Invalid / Blocked Number: The handset is offline, not on WhatsApp, or has blocked your number.
• Template Status: Pending, Rejected, Paused (spam reports) or Deleted templates cannot be sent.
• 24-Hour Service Window: Free-form text is restricted to 24 hours after the customer’s last incoming message; use an approved template outside this window.
• Insufficient Wallet Balance: If the prepaid wallet cannot cover Meta’s per-delivered-message fee, dispatch stops; failed messages cost ₹0 and the amount auto-credits back.

Follow this diagnostic workflow:

1. Open WhatsApp → Reports / Campaign Logs in the panel and note the exact error code.
2. Send a Utility template to the same number. If it delivers but a Marketing template fails, the cause is 131049.
3. Send the campaign to an internal test handset. If only the customer fails, their number is invalid/offline/blocked. If all fail, check template status and wallet balance.
4. Open the CSV file and ensure placeholders {{1}}, {{2}}, etc. match Meta template variables precisely with no blank cells or stray characters.
5. Confirm available balance on the wallet and, if needed, review detailed rates on the MyOperator Pricing Page.

5. Campaign & Chat Errors

An error reading “Name already in use” appears when another campaign holds the identical name. Rename the new campaign and reschedule.

If the chat page shows “Something went wrong”, earlier unsupported URLs triggered the failure. A product fix now replaces such content with an “unsupported message” label so the chat window remains stable.

6. Facebook API Failures & Account Connectivity

“Facebook API Failed” during number onboarding means the WABA was deliberately disconnected in FBM. Re-run onboarding via WhatsApp → Accounts → Add New Number and reconnect billing.

The same error appearing anywhere in the panel signifies either a blocked Meta account or a severed billing link. First check status in FBM; if Rejected/Blocked, appeal to Meta. If Active, restart the complete onboarding flow to reconnect the billing system.

7. WABA Status Visibility & "Unreachable" Condition

The panel now shows four explicit statuses for each WABA account:

• Approved
• Pending
• Rejected
• Unreachable – billing credit line removed, account migrated to another provider, or account deleted

Phone-number status remains independent. When WABA is Unreachable, MyOperator halts webhook fetching. To resolve: log into Meta Business Manager (business.facebook.com) → Business Settings → Billing & Payments and verify the BSP credit line or payment method is active, then return to the MyOperator panel and click Sync Now to refresh the status. If the account was intentionally deleted or migrated, a fresh WABA onboarding process is required.

8. Handling Rejections & Blue Tick Verification

If a WABA or phone shows Rejected, no further number verification is allowed until Meta clears the appeal. Compare the legal name, website, and email with government proof, then submit an appeal with the GST Certificate, Incorporation Certificate, or a Utility Bill under Direct Support → Request Review.

Blue Tick (Official Business Account) requirements:

• WABA status: Live / Connected
• Meta Business Verification completed
• Two-Step Verification enabled on the phone number
• Messaging Tier 1 or higher (≥1,000 business-initiated conversations per day recommended)
• Demonstrable brand notability (press, Wikipedia, etc.)

Apply in WhatsApp Manager → Account Tools → Phone Numbers → Settings → Profile → Official Business Account → Submit Request with up to five media links. If declined, wait 30 days before re-applying.

9. Escalation Paths & Support

Escalate to your Account Manager for:

• Prepaid wallet top-ups or rate-card reviews
• Raising Meta daily messaging limits (e.g., from 1 k to 10 k)
• Appeals for Business Verification rejections or restoring disconnected billing credit lines

Internal Support escalates directly to Tech Support when:

• Server-level API timeouts or webhook drops occur on approved templates despite sufficient balance
• OTP transcription fails repeatedly on virtual numbers with a clean IVR
• Manual Sync Now leaves status stuck

Contact Support:

• Phone: +91 81029 81029
• Email: support@myoperator.com

Keywords

WABA troubleshooting, WhatsApp Business API errors, 131049, 131026, 136024, Facebook API Failed, Unreachable status, OTP verification, template rejection, MyOperator WhatsApp, marketing frequency cap, IVR forwarding, Meta Business Manager, blue tick verification