WhatsApp error 133004: server temporarily unavailable

What does WhatsApp error 133004 mean?

It means the platform could not process the request at that moment because a server was unavailable.

Meta lists 133004 in the Cloud API error reference with the details text "Server is temporarily unavailable." The word temporarily is the key part. Nothing about the access token, the number or the message is being rejected, and the same request may succeed a short while later.

It appears among the 133 codes, most of which concern registering and deregistering phone numbers, so it is commonly met during a registration call. Meta does not restrict it to registration, though, so treat it as a server condition wherever it shows up.

What should you check before retrying?

Two things, both named in Meta's own remedy.

First, the WhatsApp Business Platform Status page at metastatus.com. If Meta is reporting an incident, retrying is pointless until it clears, and the page is a faster answer than your own logs.

Second, the details value inside error_data in the response. Meta's error reference describes details as the most likely reason for the error, sometimes with guidance on what to do. For this code Meta specifically says to check it before trying again. If the status page is clear and details gives no wait time, retry with an increasing delay rather than immediately.

How is 133004 different from other temporary errors?

Meta lists several codes that describe something being briefly unavailable, and they are worth keeping apart in logs.

Code 1 is described as an invalid request or possible server error, code 2 as temporary due to downtime or overload, and 131016 as a service being temporarily unavailable. 133004 names a server specifically.

The handling is similar for all of them: confirm platform status, read the details value, and back off before retrying. Logging the exact code still matters, because a cluster of one code at one time of day tells Meta support far more than a generic note that the API was down.

Common mistakes

• Retrying instantly in a tight loop. A server that is down stays down for the next millisecond too.
• Skipping the details value. Meta says to read it before retrying, and it may carry the reason.
• Changing the request to work around it. Nothing in the request caused the error.

Frequently asked questions

Keep reading