Troubleshooting common WhatsApp connection errors

Diagnose and fix the most common errors when connecting or using WhatsApp in Omnifox.

Jun 22, 2026

Connecting WhatsApp to Omnifox is usually quick. When it fails, it is nearly always one of a handful of known problems. This guide helps you spot them.

Before you start

  • Check that your Meta Business account is verified.
  • Have admin access to Omnifox and to your WhatsApp Business account.

The Meta window doesn't open

The wizard opens a pop-up. If nothing appears:

  • Disable the pop-up blocker for omnifox.io and click the button again.
  • If you are inside another app's in-app browser (Instagram, Facebook), open Omnifox in Chrome or Safari instead.
  • If the window opens blank, close it, go back to Settings → Channels and restart the process.

The wizard won't let me continue

If clicking a card shows "Poné un nombre para el canal antes de conectar", the channel name field at the top is empty. Fill it in and click again.

Error: the number is already in use

  • A number can only be connected to one platform at a time.
  • If it already lives on another Cloud API platform, use Migrate existing number instead of creating a new one, or release it there first.
  • For Coexistence the number must not be migrated to another Cloud API platform — that's one of the requirements the wizard asks you to confirm.

Messages don't reach the inbox

  1. Check under Channels that the channel shows as Connected and not Error.
  2. Don't look for a reconnect or refresh-webhook button: there isn't one, and the webhook registers automatically on connect. If the channel is in error, run the wizard again with the same number (see the reconnection article).
  3. Send a test message from another phone.

Error: code 190 — every send fails

  • The channel's access token expired.
  • Fix: connect the channel again with the same number to refresh the token.
  • Also check that the system user in Meta wasn't deleted.

Error: #131009 when sending templates

  • Usually caused by duplicate titles or IDs in buttons or lists.
  • Meta requires every button, list row or SKU to have a unique identifier.
  • Edit the template, make the identifiers unique and resubmit.

The template was rejected

  • Review the category (Marketing / Utility / Authentication).
  • Add sample values to every variable.
  • Fix spelling, suspicious links or incomplete text.

The Coexistence history never arrived

History is shared during pairing, when Meta asks you. If you didn't accept then, the only way to get it is to pair the number again.

Final tip: when things break all at once without you changing anything, suspect an expired token (code 190). Reconnecting the channel fixes most mass-send failures.

Related articles

Was this helpful?

Related articles

Message us on WhatsApp