Messenger Platform · error code

Messenger error 10: Page restricted from opt-in requests

Policy / accountHTTP 403Policy & restrictions

Last verified against Meta for Developers - Messenger Platform error codes

What Messenger returns
Application does not have permission for this action

What error 10 means

Code 10 with subcode 1404170 returns the generic string "Application does not have permission for this action," but Meta's error-codes table pins the actual meaning: it fires "when the Page is temporarily restricted from sending Marketing Message opt-in requests." The Page asked too many people, or the wrong people, too often, for permission to send recurring marketing notifications, and the platform has paused the Page's ability to ask.

The marketing-messages system is consent-driven, and Meta polices the consent-gathering step as firmly as the sending step. Related controls surround this one: 10/1893015 when a person has stopped a topic, the documented code 9/2018352 family when the opt-in request limit per user is exceeded, and the legacy 613/1893016 rule against repeated opt-in requests on the same topic. Subcode 1404170 is the Page-level consequence when the pattern persists: not one user's refusal, but a restriction on the Page's opt-in machinery itself.

The restriction is temporary, with no duration in the error. While it lasts, opt-in request sends fail, but existing opted-in audiences and normal conversation are unaffected, another error best handled per-feature rather than globally. The signal to act on is behavioral: your opt-in prompting is too aggressive for your audience, and resuming the same pattern after the restriction lifts invites a longer one, on the same ladder that ends at 368.

What it looks like

{
  "error": {
    "message": "(#10) Application does not have permission for this action",
    "type": "OAuthException",
    "code": 10,
    "error_subcode": 1404170,
    "fbtrace_id": "BLBz/WZt8dN"
  }
}

Why it happens

  • Opt-in requests fired at every user indiscriminately (e.g. on first contact) rather than at engaged moments.
  • Repeated requests to users who ignored or declined earlier prompts.
  • High decline or block rates on the Page's opt-in request messages.
  • Multiple flows independently prompting the same audience.
  • Resuming aggressive prompting immediately after a previous restriction.

How to fix Messenger error 10

  1. 1Stop sending opt-in requests and let the restriction expire; test cautiously with low volume before resuming.
  2. 2Gate future prompts on engagement signals (active conversation, completed purchase) instead of blanket triggers.
  3. 3Suppress users who declined or ignored a prompt from being asked again soon.
  4. 4Consolidate prompting into one flow with per-user frequency caps.
  5. 5Check Page Quality in Business Suite for any accompanying notices or appeals.

How to stop it recurring

Ask for marketing consent the way a good salesperson would: rarely, at the right moment, and never twice in a row. Encode per-user prompt budgets and engagement preconditions, and measure accept rates, a low one predicts this restriction. The marketing-messages rules sit with the other volume controls in the Messenger limits reference, and the consent-system errors are cross-linked from 10/1893015.

Official reference: Meta for Developers - Messenger Platform error codes. See all Messenger error codes or the Messenger limits and quotas.

Related codes

Error 10 - quick answers

What does Messenger error 10 mean?

Code 10 with subcode 1404170 returns the generic string "Application does not have permission for this action," but Meta's error-codes table pins the actual meaning: it fires "when the Page is temporarily restricted from sending Marketing Message opt-in requests." The Page asked too many people, or the wrong people, too often, for permission to send recurring marketing notifications, and the platform has paused the P

How do I fix Messenger error 10?

1. Stop sending opt-in requests and let the restriction expire; test cautiously with low volume before resuming. 2. Gate future prompts on engagement signals (active conversation, completed purchase) instead of blanket triggers. 3. Suppress users who declined or ignored a prompt from being asked again soon. 4. Consolidate prompting into one flow with per-user frequency caps. 5. Check Page Quality in Business Suite for any accompanying notices or appeals.

Stop debugging Messenger by hand

Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.