Reconnect a disconnected WhatsApp channel
Your WhatsApp channel stopped sending or shows an Error badge. Follow this step-by-step diagnosis to reconnect it and get back to chatting.
When you need to reconnect
If your WhatsApp number stops sending or the channel shows Error under Settings → Channels, the connection with Meta has most likely broken — almost always an expired token. Reconnecting usually fixes it in a couple of minutes.
Before you start: you need to sign in with the same Facebook account you used to connect the number, and have admin rights in Meta Business Manager.
Step 1: diagnose
- Channel shows Error: almost always expired credentials. Reconnecting fixes it.
- Receives but doesn't send: could be a temporary Meta outage. Wait a few minutes before reconnecting.
- Only templates fail: not a disconnection; check the template status in Meta.
- A single contact fails: check whether the 24-hour window closed; if so you need a template.
Step 2: reconnect
Omnifox has no "Reconnect" button. If you open the channel from the list you'll see the notice "Omnifox administra automáticamente las credenciales de este canal" — that's correct: credentials are not edited by hand.
To reconnect, run the wizard again with the same number:
- Go to Settings → Channels and click Connect New Channel.
- Pick WhatsApp and type a channel name.
- Click the same card you used the first time: Connect with WhatsApp if the number is on Coexistence, or Migrate my number / Create a new number if it's on Cloud API.
- Complete the Meta window with the same account and the same number.
Even though the button says "connect new channel", no duplicate is created: Omnifox recognises the number by its Phone Number ID within the same workspace, updates the existing channel, refreshes the token and sets it back to Connected. Your conversations, contacts and templates are kept.
Step 3: verify
- Confirm the channel status changed to Connected.
- Send a test message to a contact with an open window, or an approved template.
- Check the message goes out with the double tick.
If it still fails
- Still in Error: sign out of Facebook in another tab and retry with the right account. Check that the Omnifox app still holds its permissions in Meta.
- The Meta window doesn't open: disable the pop-up blocker for omnifox.io.
- The number is connected elsewhere: release or migrate it from that platform first.
- The history didn't come back: on Coexistence, history is requested once at pairing time. To pull it again you have to re-pair the number.
Tips
- Don't delete the channel to recreate it: reconnecting keeps your conversations; deleting starts from zero.
- If drops are frequent, ask your admin to use a non-expiring System User token.
Related articles
Related articles
-
WhatsApp (Meta) error codes: what they mean and what to do
A table of the most common Meta error codes when sending on WhatsApp (131026, 131047, 131049, 130497, 141006, 131031, 131056, 132000, 190, 368…) and how to fix each one.
-
How to connect Telegram
Connect a Telegram bot to your Omnifox inbox in minutes using BotFather.
-
Instagram and Facebook comments: reply and moderate from Omnifox
See and answer comments on your Facebook and Instagram posts and ads, publicly or privately, and set up automatic replies.
-
Sending and receiving videos on each channel: formats and size limits
Which videos you can send and receive on WhatsApp, Instagram, Messenger, Telegram, web chat and email, the real size limits, and what to do with a large video.
-
Move from WhatsApp QR to Coexistence or Cloud API
Once you're done testing with the QR code, move your number to the official connection: no caps, with templates and broadcasts, and no volume-based ban risk.