Messenger error 613: Duplicate opt-in request for the same topic
Last verified against Meta for Developers - Messenger Platform error codes
Scope of service exceeded: You may not send multiple opt-in requests with the same topic to a user.What error 613 means
Code 613 with subcode 1893016 fires "when a Page sends more than 1 opt-in request to the user on the same topic," according to Meta's error-codes table. The literal text: "Scope of service exceeded: You may not send multiple opt-in requests with the same topic to a user." In marketing messages on Messenger, each opt-in request names a topic, and a person gets asked about a given topic once.
Although it uses 613, the code family for rate limiting, this is not a throughput problem. Waiting a minute and retrying returns the same error, because the rule is per person per topic, not per second.
Meta's table adds a practical note for the Send to Messenger opt-in path: if the person hits this error while opting in through that plugin on your website, you should tell them on the site that an opt-in request was already sent to them in Messenger. In other words, the person may simply have an earlier request waiting in their thread. Related but different: 9/2018352 is the Page-wide cap on requests, and 10/1893015 is a person who opted out.
What it looks like
{
"error": {
"message": "(#613) Scope of service exceeded: You may not send multiple opt-in requests with the same topic to a user.",
"type": "OAuthException",
"code": 613,
"error_subcode": 1893016,
"fbtrace_id": "BLBz/WZt8dN"
}
}Why it happens
- Sending a second opt-in request for a topic the person was already asked about.
- Campaign tools that re-ask everyone who did not respond to the first request.
- Two systems on the same Page requesting the same topic independently.
- A website Send to Messenger flow triggered again by a returning visitor.
How to fix Messenger error 613
- 1Do not retry; mark the (PSID, topic) pair as already requested.
- 2If the request came from Send to Messenger on your site, show a message that the request is already waiting in Messenger.
- 3Check stored opt-in state before every request, including requests that went unanswered.
- 4Use a distinct topic only when the content is genuinely different, not to work around the rule.
How to stop it recurring
Store every opt-in request you send, with topic and timestamp, alongside the tokens you receive back, and make the request path check that table first. Unanswered asks count as asked. The marketing-messages rules are summarized 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
- 9: Too many marketing message opt-in requestsUser is performing too many actions
- 10: Page restricted from opt-in requestsApplication does not have permission for this action
- 10: User stopped notification messages for this topic(#10) This user has currently stopped notification messages for this topic
- 4: Minimum delay between marketing notificationsMarketing Messages - There has to be a minimum delay between 2 notifications…
Error 613 - quick answers
What does Messenger error 613 mean?
Code 613 with subcode 1893016 fires "when a Page sends more than 1 opt-in request to the user on the same topic," according to Meta's error-codes table. The literal text: "Scope of service exceeded: You may not send multiple opt-in requests with the same topic to a user." In marketing messages on Messenger, each opt-in request names a topic, and a person gets asked about a given topic once.
How do I fix Messenger error 613?
1. Do not retry; mark the (PSID, topic) pair as already requested. 2. If the request came from Send to Messenger on your site, show a message that the request is already waiting in Messenger. 3. Check stored opt-in state before every request, including requests that went unanswered. 4. Use a distinct topic only when the content is genuinely different, not to work around the rule.
Should I retry after error 613?
No. Retrying the same request produces the same error; the condition has to be fixed first. Treat it as a permanent failure for that message and surface it, rather than looping.
Stop debugging Messenger by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.