Messenger error 9: Too many marketing message opt-in requests
Last verified against Meta for Developers - Messenger Platform error codes
User is performing too many actionsWhat error 9 means
Code 9 with subcode 2018352 returns the terse "User is performing too many actions," but Meta's error-codes table gives the specific trigger on Messenger: it fires "when the Marketing Message opt-in request limit has been exceeded." Marketing messages on Messenger, the feature that replaced recurring notifications, require the business to ask each person for permission with an opt-in request before it can send them promotional notifications outside the standard window. Meta caps how many of those requests a Page can send.
So the "user" in the message is effectively your Page acting through the API, not the customer misbehaving. The send that failed was the permission ask, and no opt-in message reached the person.
Keep it apart from its neighbors. 613/1893016 means you asked the same person about the same topic twice; 10/1404170 means the Page has been temporarily restricted from asking at all. 2018352 is a volume cap that clears with time, but pushing against it repeatedly is the kind of pattern that leads toward the restriction.
What it looks like
{
"error": {
"message": "(#9) User is performing too many actions",
"type": "OAuthException",
"code": 9,
"error_subcode": 2018352,
"fbtrace_id": "BLBz/WZt8dN"
}
}Why it happens
- Bulk opt-in campaigns that send the request to a large audience in a short burst.
- Bots that attach an opt-in request to every conversation instead of moments where the person has shown interest.
- Several tools on the same Page each sending opt-in requests independently.
- Retry loops that resend failed opt-in requests without delay.
How to fix Messenger error 9
- 1Stop sending opt-in requests for now and queue the remainder of the campaign.
- 2Resume at a lower pace, spreading requests over time instead of bursting.
- 3Deduplicate across tools so each person receives at most one request per topic.
- 4Target the request to people who just engaged, where acceptance is likely.
- 5Track request counts per Page so you can see when you are approaching the cap.
How to stop it recurring
Treat the opt-in request as a scarce resource. Ask in context, after a purchase question or a back-in-stock inquiry, rather than broadcasting asks to your whole contact list. Keep one shared ledger of who was asked about which topic and when, and throttle campaign tooling against it. The marketing-messages rules sit with the other window rules in the Messenger limits reference.
Official reference: Meta for Developers - Messenger Platform error codes. See all Messenger error codes or the Messenger limits and quotas.
Related codes
- 613: Duplicate opt-in request for the same topicScope of service exceeded: You may not send multiple opt-in requests with the…
- 10: Page restricted from opt-in requestsApplication does not have permission for this action
- 4: Minimum delay between marketing notificationsMarketing Messages - There has to be a minimum delay between 2 notifications…
- 10: User stopped notification messages for this topic(#10) This user has currently stopped notification messages for this topic
Error 9 - quick answers
What does Messenger error 9 mean?
Code 9 with subcode 2018352 returns the terse "User is performing too many actions," but Meta's error-codes table gives the specific trigger on Messenger: it fires "when the Marketing Message opt-in request limit has been exceeded." Marketing messages on Messenger, the feature that replaced recurring notifications, require the business to ask each person for permission with an opt-in request before it can send them p
How do I fix Messenger error 9?
1. Stop sending opt-in requests for now and queue the remainder of the campaign. 2. Resume at a lower pace, spreading requests over time instead of bursting. 3. Deduplicate across tools so each person receives at most one request per topic. 4. Target the request to people who just engaged, where acceptance is likely. 5. Track request counts per Page so you can see when you are approaching the cap.
Can I retry after error 9?
Yes - this is a retryable condition. Back off (start around one second and double on each attempt, with jitter) and watch for a retry-after hint from the platform before resending.
Stop debugging Messenger by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.