Failed to save credentials
MsgOrb now shows Meta's own rejection text rather than a generic message. Read the alert carefully — it names the cause.
The usual causes, in order of frequency:
- 1The WABA ID field holds a Phone Number ID. They are different IDs. Meta refuses to validate a phone-number node as a Business Account. Get the correct value from Meta → WhatsApp → API Setup, under *WhatsApp Business Account ID*.
- 2The token has expired. Meta replies *Session has expired*. Generate a permanent System User token — see Access tokens and permissions.
- 3The token lacks permissions. It needs both
whatsapp_business_messagingandwhatsapp_business_management. - 4The token belongs to a different business. The system user must have both your app and your WABA assigned as assets.
A failed save is a no-op: MsgOrb validates before it writes, so a rejected attempt never damages a working connection.
The connect button does nothing
Connect with Facebook needs Meta's script to have loaded. Reload the page, and make sure a browser extension or content blocker is not blocking connect.facebook.net. If the Meta window opens and closes without a result, MsgOrb falls back after fifteen seconds and exchanges the authorisation code on its own.
Connected, but nothing sends
Being connected only means the credentials are valid. Proactive messages still need an approved template. Start with Nothing is being delivered.
Active Subscription Required
The connection fields stay disabled until the workspace has an active paid plan. Open Billing.