Skip to content
Meta Business PartnerAPI error reference

WhatsApp API error 131016: Service unavailable

Error 131016 means part of the WhatsApp service was temporarily unavailable when you sent. It's a Meta-side outage or overload, not a problem with your account or your message.

131016
Code
Service unavailable
Meta's name
Meta service
Type
API response or failure webhook
Where you see it
Yes, with backoff
Retry

Quick answer

A WhatsApp service was briefly unavailable. Check Meta's platform status, queue the messages and retry with backoff.

What WhatsApp error 131016 means

Meta documents 131016 as: a service is temporarily unavailable, and advises checking the WhatsApp Business Platform status page before trying again.

Why error 131016 happens

This one starts on Meta's side, though your request can play a part. Likely causes:

  • A partial outage on Meta's side.
  • Heavy load on the platform during a peak.
  • Maintenance affecting a particular service.
  • A network problem between your provider and Meta during an incident.

How to fix error 131016

Most of the work is making your sending resilient so this resolves itself.

  • Check the WhatsApp Business Platform status page.
  • Put failed messages back in a queue instead of dropping them.
  • Retry with exponential backoff and jitter so retries don't arrive all at once.
  • Prioritise time-critical messages, such as one-time codes, when the service returns.
  • Make retries idempotent by reusing your own message reference, so a message isn't sent twice when a retry overlaps a late success.

Should you retry after 131016?

Retry with backoff. If the outage is long, decide whether time-sensitive messages are still worth sending, or send them by another channel.

How error 131016 shows up in InfiQ

When the send is refused on the spot, the InfiQ API response holds Meta's error object unchanged (code 131016, the "(#131016)" message and error_data.details) alongside InfiQ's own InfiQ_traceid. When the failure only shows up after the send was accepted, it arrives as a message.failed webhook whose data.error.metaErrorCode is 131016, tied to the original message. Treat both the same way in your error handling. Keep the trace IDs with the failed message: they are what support needs to look it up.

Send it through InfiQ

Frequently asked questions

Do I pay for messages that fail with 131016?+
Meta charges for delivered messages, and a message that failed with 131016 wasn't delivered. Resending it, once it is delivered, is charged as a normal message.
Is error 131016 the same as error 2?+
They describe the same situation from different layers. Code 2 is a general platform code for temporary downtime or overload; 131016 is WhatsApp's own "service unavailable". Handle both with queued retries and backoff.
How long should I keep retrying after 131016?+
Set a limit by message type. A one-time code is useless after a few minutes, so stop and offer another channel; an order update can keep retrying for hours. Without a limit, a long outage turns into a burst of stale messages.

Retries handled, failures explained

InfiQ returns Meta's error with its own trace ID and posts failures to your webhook, so outages don't lose messages silently.