← Back to Blog
product-update byon diagnostics whatsapp-cloud-api troubleshooting

Meta Returned 200 but the Message Never Arrived: Number Diagnostics in PipesBot

Ler em português →

Short version: a 200 OK with a wamid from the WhatsApp Cloud API means “accepted”, not “delivered”. If the number, its WABA or the business behind it is blocked, Meta still accepts the send and reports the failure later, if you’re listening. The Check Health button on BYON numbers is now Diagnostics: it asks Meta what’s blocking each part of the chain, shows the suggested fix, and lets you send a test message to see Meta’s raw answer. The same data is available at GET /v1/pool-numbers/:id/health.

The bug report that started this

A customer wrote in: “Inbound works. My bot replies. The API returns success. Nobody receives anything.”

Everything on our side looked healthy. The access token was valid, webhooks were arriving, and every send came back with a message id. The cause was one level up: the WABA had been blocked because its payment method failed (Meta error 141006). Since October 1, service messages are billed past the free tier, so a missing or failing card now stops delivery.

Meta didn’t reject the sends. It accepted them, then sent a failed status webhook a little later. If your integration ignores statuses (and legacy Apps never received them), the messages just disappear.

Our old health check only tested whether the token worked, so it said “active.” It was right about the token and useless for this problem.

What Diagnostics checks

Meta exposes a health_status on every phone number that covers each entity in the chain: the phone number, the WABA, the business portfolio and the app. For each one, Meta says whether it can send messages (AVAILABLE, LIMITED or BLOCKED), which errors are blocking it, and what to do about it.

Open your App’s Numbers tab and click Diagnostics on a BYON number. The dialog shows:

  • The verdict: can this number send messages right now?
  • One badge per entity with its blocking errors, Meta’s suggested fix, and extra info, such as a display name still waiting for approval.
  • Phone details: connection status, name status, platform, quality rating and messaging limit tier.
  • A test send: pick a template or a text, send it to a number you control, and see Meta’s exact HTTP status and body.

Calling-related errors (the 138xxx range) show up in the same Meta list, but they don’t affect messaging, so we label them separately. A number with a SIP problem can still send messages fine.

Running Diagnostics also refreshes the number’s token health: it becomes unhealthy when Meta rejects the token and goes back to active after a successful check.

Same data over the API

If you run a platform on top of PipesBot, your customers will ask you “why aren’t my messages going out?” Now you can answer from your own admin panel:

curl https://api.pipes.bot/v1/pool-numbers/pn_abc123/health \
  -H "Authorization: Bearer ak_your_app_key"
{
  "checkedAt": "2026-10-25T13:02:11.000Z",
  "canSendMessage": "BLOCKED",
  "entities": [
    { "type": "PHONE_NUMBER", "id": "1098765432", "canSendMessage": "AVAILABLE", "errors": [], "additionalInfo": [] },
    {
      "type": "WABA",
      "id": "2233445566",
      "canSendMessage": "BLOCKED",
      "errors": [
        {
          "code": 141006,
          "description": "There is an error with the payment method. This will block business initiated conversations.",
          "solution": "There was an error with your payment method. Please add a new payment method to the account.",
          "area": "messaging"
        }
      ],
      "additionalInfo": []
    }
  ],
  "phone": { "displayPhoneNumber": "+55 11 98765-4321", "status": "CONNECTED", "qualityRating": "GREEN", "messagingLimitTier": "TIER_250" },
  "error": null
}

The endpoint takes an App key (ak_) and works even when a number is half-broken, which is exactly when you need it. If Meta can’t be queried at all (expired token, wrong id), canSendMessage is null and error explains why, with tokenInvalid set for token problems.

Habits worth adopting

Diagnostics tells you why a number is blocked. These habits help you notice sooner:

  • Read failed statuses. On API v2, statuses are delivered to your webhook. A spike in failed is your earliest warning.
  • Keep a valid payment method on the WABA. A failing one blocks business-initiated conversations (that’s what 141006 says), and service messages stop once a number goes past the 1,000 free each month.
  • Check before you blame the bot. When a customer says “the bot went quiet”, run Diagnostics first. It takes a few seconds and rules out a whole class of problems that no code change will fix.

Diagnostics is live now for every BYON number in the dashboard. The API reference is in Number Management.