Channel status and health
How Omnifox monitors your channels with automatic health checks every 5 minutes, what each status means (Connected, Error, Paused), and what to do when a channel goes down.
Omnifox automatically watches the health of every connected channel so you find out about a problem before your customers do. This guide explains how the check works, what each status means, and how to recover a channel that stopped sending or receiving messages.
How the health check works
Every 5 minutes, Omnifox pings the API of each active channel (WhatsApp, Messenger, Instagram, Telegram, Web Chat, and more) using the stored credentials. Based on the response it updates the channel status and records the time under Last check.
- Paused channels are not checked: pausing a channel stops its health check and alerts.
- If a channel type has no verification adapter, its status is left untouched so it never flaps with false alarms.
What each status means
In the channel list (the Channels menu) each channel shows a colored badge:
- Connected (green): the last check returned OK. The channel sends and receives normally.
- Pending (amber): the channel is half-configured or awaiting verification (for example, a webhook not yet confirmed).
- Error (red): the last check failed. Next to the badge you will see the error message returned by the provider.
- Disconnected (gray): the channel is not active.
- Paused: a badge showing an operator stopped the channel manually.
How to check a channel's status
- Open Channels from your workspace settings.
- Find the channel in the list and look at its status badge and the Last check timestamp.
- To force an immediate verification, click the Health Check button (pulse icon) on that row.
- If the status is Error, read the red message: it usually names the cause (expired token, dead webhook, missing permissions).
Verification
A healthy channel shows Connected in green and a recent Last check time (under 5 minutes). Send a test message from the Inbox to confirm real end-to-end delivery.
If it isn't working
- Error mentioning "token" or code 190 (WhatsApp/Meta): the channel's access token expired. Reconnect the channel by running the connection flow (Embedded Signup) again to refresh the credentials.
- Webhook error: re-register the webhook from the channel's connection wizard.
- The channel is Paused: turn it back on with the Reactivate button — this restores the health check and fires an immediate verification.
- Still in Error after reconnecting: confirm the app or number is still active on the provider side (Meta Business, BotFather, etc.).
Tips
Pause a channel instead of disconnecting it during maintenance: you avoid noisy error alerts and keep all of its configuration.
Never share or reuse a channel's credentials across accounts: a token revoked elsewhere will push your channel into Error.
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.