WhatsApp API error 131050: User has stopped marketing messages
Error 131050 means the person has told WhatsApp they no longer want marketing messages from your business. WhatsApp will not deliver your marketing templates to them, however often you try.
Quick answer
The customer stopped marketing messages from you in WhatsApp. Mark them as opted out of marketing, keep sending only the service and utility messages they still expect, and do not retry the marketing message.What WhatsApp error 131050 means
Meta documents 131050 as a delivery error: the recipient has chosen to stop receiving marketing messages on WhatsApp from your business. Meta's advice is not to retry, because those messages will not be received. It concerns marketing only, so it is a preference, not a block.
Why error 131050 happens
The message itself was fine; something about the recipient or your relationship with them stopped it. Typical triggers:
- The customer used WhatsApp's option to stop marketing messages from your business after an earlier campaign.
- Your list kept sending marketing templates to someone who had already opted out, because the preference was never recorded.
- Several brands share one list and the customer opted out of all promotional messages from your number.
How to fix error 131050
There is no request change that gets this message delivered; the work is in your data and your audience.
- Record a marketing opt-out on the contact as soon as you see 131050.
- Exclude opted-out contacts from every future marketing audience before the campaign is sent, not after it fails.
- Keep sending utility messages the customer needs, such as order updates or payment receipts, using utility templates.
- If the customer opts back in, for example by asking for offers in a chat, record the new consent with its date before marketing to them again.
Should you retry after 131050?
Never retry a marketing message after 131050: it will not be delivered, and repeated attempts only cost you engagement signals. The customer can resume marketing messages themselves; until they do, leave them out of campaigns.
How error 131050 shows up in InfiQ
When the send is refused on the spot, the InfiQ API response holds Meta's error object unchanged (code 131050, the "(#131050)" 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 131050, 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. Treat this code as an opt-out signal in your own systems too: sync it back to your CRM so the next campaign tool does not add the contact again.
Frequently asked questions
Can I still send order updates after error 131050?+
How do I know when a customer turns marketing messages back on?+
See every failed delivery, with the reason
InfiQ passes Meta's error code and details through on every failed message, so your team knows whether to fix, wait or drop it.