Messenger error 2022: Commerce messaging temporarily disabled
Last verified against Meta for Developers - Messenger Platform error codes
The ability to send commerce messages has been temporarily disabled. This is the result of a feature limit placed after a policy violation.What error 2022 means
Code 2022 is a feature-scoped enforcement action: "The ability to send commerce messages has been temporarily disabled. This is the result of a feature limit placed after a policy violation." Unlike the blanket policy block 368, this one names its scope, commerce messaging, and its cause, a violation that has already been adjudicated. The Page or app crossed a commerce-policy line, and Meta responded by switching off that capability class for a period.
Commerce messaging covers the transactional surfaces Messenger offers around selling: order-related flows, product templates and the commerce-adjacent message types. Violations that draw this limit typically involve prohibited goods or services, misleading transaction claims, or misuse of purchase-flavored messaging for promotion. The word "temporarily" is genuine, feature limits expire, but the duration is not returned in the error, and repeated violations escalate in length and scope.
Operationally, 2022 splits your bot's traffic: ordinary conversation continues to work while the commerce-flavored sends fail. A bot that treats it as a global outage will look broken everywhere; a bot that catches it per-feature can degrade cleanly, keep answering questions, take orders through a webview or website link instead, and tell staff why the product carousel stopped rendering. The authoritative place to see the restriction, its reason and any appeal path is the Page's account-quality surfaces in Meta Business Suite, not the API.
What it looks like
{
"error": {
"message": "(#2022) The ability to send commerce messages has been temporarily disabled. This is the result of a feature limit placed after a policy violation.",
"type": "OAuthException",
"code": 2022,
"fbtrace_id": "BLBz/WZt8dN"
}
}Why it happens
- Commerce-policy violations: prohibited or restricted goods promoted through messaging.
- Misleading purchase or order communications flagged by review.
- Repeated user reports on commerce-flavored messages from the Page.
- Promotion disguised as transactional messaging.
- Accumulated smaller violations crossing an enforcement threshold.
How to fix Messenger error 2022
- 1Check Page Quality / Account Quality in Meta Business Suite for the specific violation, duration and appeal option.
- 2Appeal there if you believe the enforcement is mistaken; the API offers no appeal path.
- 3Gate commerce features behind a capability flag your error handler can flip, so the rest of the bot keeps working.
- 4Route purchases through your website via URL buttons while the limit lasts.
- 5Before re-enabling, review the flows against the commerce policy so the next limit is not longer.
How to stop it recurring
Keep commerce messaging strictly transactional and compliant: sell only permitted goods, describe orders accurately, and keep promotion inside the surfaces built for it. Review Meta's commerce policies whenever the catalogue changes, category drift is how compliant Pages become non-compliant. Feature-scoped enforcement and its escalation ladder are discussed alongside 368 in this catalogue and in the Messenger troubleshooting guide.
Official reference: Meta for Developers - Messenger Platform error codes. See all Messenger error codes or the Messenger limits and quotas.
Related codes
Error 2022 - quick answers
What does Messenger error 2022 mean?
Code 2022 is a feature-scoped enforcement action: "The ability to send commerce messages has been temporarily disabled. This is the result of a feature limit placed after a policy violation." Unlike the blanket policy block 368 , this one names its scope, commerce messaging, and its cause, a violation that has already been adjudicated.
How do I fix Messenger error 2022?
1. Check Page Quality / Account Quality in Meta Business Suite for the specific violation, duration and appeal option. 2. Appeal there if you believe the enforcement is mistaken; the API offers no appeal path. 3. Gate commerce features behind a capability flag your error handler can flip, so the rest of the bot keeps working. 4. Route purchases through your website via URL buttons while the limit lasts. 5. Before re-enabling, review the flows against the commerce policy so…
Stop debugging Messenger by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.