Errors Meta returns during setup
The Meta-side failures OMAI recognises when you connect a number: the message you see, what it actually means, and the fix — plus what to send us when only the generic error appears.
- Who
- Owners and admins
- Plan
- All plans
- Role
- Owner or Admin
Before you start
- You are part-way through connecting a number, or a card is showing Action required
Connecting a number is a conversation between three parties: you, Meta and OMAI. Meta decides whether the number may be used, and when it refuses, OMAI translates the refusal into one sentence you can act on. This article lists the refusals the product actually recognises — not Meta’s whole error catalogue.
Where a Meta problem shows up
- On the connect card, while you are in the middle of connecting — a short red line under the button.
- On the number’s card afterwards, as an orange guidance line under an Action required badge.
- Under Technical details on that card, as a raw
detailcode. This is the value support needs.
Problems while Meta’s window is open
| What you see | What it really means | The fix |
|---|---|---|
| Login was canceled. | Meta’s window closed without returning a result — usually because it was closed early or a permission was declined. | Press the connect button again and complete every step in the window. |
| No number details received from Meta. Please try again. | The window finished, but Meta sent back no business account and no number, so there is nothing to connect. | Try once more. If it repeats, run the guided check first — it identifies which path your number belongs on. |
| Still loading — please try again in a moment. | Meta’s script had not finished loading in your browser when you pressed the button. | Wait a moment, then press again. An ad blocker or a strict privacy extension can prevent it loading at all. |
| Connection failed. | The setup did not complete: either the request to OMAI came back with a failure, or the phone-approval safety net ran out its window. | Start again from the connect card. If the number was already approved on your phone, connecting again picks up from there. |
| Network error. | Your browser could not reach OMAI at all — this one is not Meta’s doing. | Check the internet connection and press the button again. |
| Self-connect (Embedded Signup) isn’t available right now. Please contact support and we’ll connect your number for you. | Self-connect is not switched on for this installation, so the Meta window cannot open. | Write to us and we will connect the number for you. |
| One step left — the guided check | The guided check was never finished, or the session has expired. Sessions last 60 minutes. | Press Go to the guided check, finish it, then connect. On a number that also runs on your phone, an approval you already gave on the phone is not lost — it is picked up after the check. |
| This number needs a quick review | The number is already associated with another active setup, or an earlier setup for it is still open on our side. | Use Talk to support on the panel. This one cannot be solved by trying again. |
Problems while Meta registers the number
For a number you connect through Meta’s Cloud API, the last step is registering it. If Meta refuses that step, the connection is created but lands on Action required, with one of these lines.
| What you see | What it really means | The fix |
|---|---|---|
| Reset the two-step verification PIN in WhatsApp Manager, then reconnect the number. | Meta error 133005: the number already has a two-step verification PIN and the one OMAI used does not match it. | Reset the PIN in WhatsApp Manager, then reconnect the number from the WhatsApp screen. |
| Meta allows a limited number of registration attempts per 72 hours. Wait for the window to reset, then try again. | Meta refused with a too-many-attempts message. The allowance is per number, over a rolling 72 hours. | Wait for the window to reset. Do not keep pressing connect — each attempt spends the same allowance. |
| WhatsApp couldn’t finish registering this number. Try reconnecting — if it keeps happening, contact support with the technical details below. | Any other refusal from Meta. The numeric code Meta gave is kept in the detail value on the card. | Reconnect once. If the same line comes back, open Technical details and send us the whole detail string. |
The same line, with retries_exhausted in the detail | A number left stuck on Pending verification is retried in the background at most twice, six hours apart, to protect Meta’s attempt allowance. Both retries failed. | Contact support — this one will not clear by itself. |
detail: two_step_pin_mismatch
detail: registration_rate_limited
detail: registration_failed:meta_<code>
detail: registration_failed:retries_exhaustedProblems Meta reports after the number is connected
| What you see | What it really means | The fix |
|---|---|---|
| The number was disconnected via the phone app. | Meta told us the business platform was disconnected from inside WhatsApp on the phone. | If that was a mistake, run the connect flow again from the WhatsApp screen. Otherwise remove the card. |
| Importing your contacts and chat history didn’t finish in time. | The connect-time import from your phone never reached a final state within the window Meta allows for it. | Disconnect in the phone app (Settings › Account › Business Platform), then connect again from the WhatsApp screen. |
| You chose not to share history — the inbox will fill from new conversations only. | Meta reported that history sharing was declined on the phone. It is a finished state, not a failure. | Nothing to fix. The inbox fills from new conversations. |
| Reconnect to keep receiving messages | The credential Meta issued for your business expired, was revoked, or could not be renewed. | Reconnect from the banner at the top of the WhatsApp screen. Conversations and settings are unaffected. |
| No WhatsApp capacity is available for a new number right now — you have not been charged | While buying a number, Meta refused to add another number to the WhatsApp Business Account because it is out of slots. | Nothing was charged and the rental was undone. Write to us so we can raise the capacity. |
Refusals that happen after Meta says yes
Meta can approve a number that OMAI still cannot accept — almost always because the number already exists somewhere in our system. These checks are ours, and they exist so a number can never be answered by two accounts at once.
| What you see | What it really means | The fix |
|---|---|---|
| This number is already connected to another organization | The number, or the Meta identity behind it, is connected to a different OMAI account. | Disconnect it on the other account first, then connect it here. If you do not know which account holds it, write to us. |
| This number is already connected to another account. | The same conflict, detected while the phone-approval safety net was watching for your number. | As above — the number has to be released on the other account first. |
| This number is being connected by another account. | Another account is part-way through connecting this number right now. | Wait for that attempt to finish or expire, then try again. |
| This number doesn’t match the one from your guided check. | The number being approved is not the number you entered in the guided check. | Start the guided check again with the number you actually want to connect. |
When you only see “Something went wrong”
If Meta’s API itself fails while OMAI is subscribing to your account or reading the number’s details, the connect card shows Something went wrong. Please try again. and nothing more specific. That is deliberate, not a bug in the message: the failure is recorded on our side with Meta’s code, but it is not printed on the page.
What to send us
- The phone number, in international format.
- The date and time you tried, and your time zone.
- The whole
detailline from Technical details on the card, if there is a card. - Which path you used: connecting your own number through Meta, or a number that also runs in the WhatsApp Business app on your phone.
- A screenshot of the message you saw, including anything Meta’s own window displayed.
Meta says the number is already registered. Have I broken something?
No. OMAI treats an already-registered number as a success and carries on with the setup — it is the normal answer when a number was registered on an earlier attempt.
Will OMAI change anything in WhatsApp Manager on my behalf?
It sets the display name and secures the number with a two-step verification PIN as part of setting up a number. Resetting an existing PIN is the one repair you have to do yourself, in WhatsApp Manager.
The error appeared inside Meta’s own window, not on your page.
That message comes from Meta and never reaches OMAI, so it is not stored anywhere on our side. Write it down or screenshot it before closing the window, then send it to us with the number.