Messenger Platform · error code

Messenger error 10: User thread impact

Permanent - do not retryRecipient & delivery

Last verified against Meta for Developers - Messenger Platform error codes

What Messenger returns
User Thread Impact

What error 10 means

Code 10 with subcode 2018336 is unusual because Meta documents it as a diagnostic signal rather than as a mistake in your request. The error-codes table's entry reads simply "User Thread Impact," and the explanation is a test procedure: to determine whether there is user thread impact, call the user-level menu API. "If you get a valid response, there is no impact. If you get an error message with code 10, subcode 2018336, the thread is impacted."

The user-level menu API is /me/custom_user_settings, the endpoint that overrides the Page's persistent menu for a single PSID. Meta does not publish a fuller definition of what "impacted" covers, so be careful not to read more into it than the docs say. The safe interpretation is that the conversation with this person cannot use per-thread features the way an ordinary thread can, starting with the user-level menu itself.

What it does not tell you is that the person blocked you (that is 551) or that your token is broken. Other PSIDs on the same Page behave normally.

What it looks like

{
  "error": {
    "message": "(#10) User Thread Impact",
    "type": "OAuthException",
    "code": 10,
    "error_subcode": 2018336,
    "fbtrace_id": "BLBz/WZt8dN"
  }
}

Why it happens

  • Calling GET, POST or DELETE on /me/custom_user_settings for a PSID whose thread Meta marks as impacted.
  • Setting a per-user persistent menu or composer state for that person.
  • Using the user-level menu call as a health probe, as Meta suggests, and getting a positive result.

How to fix Messenger error 10

  1. 1Probe with GET /me/custom_user_settings?psid=PSID; a valid response means no impact, 2018336 confirms it.
  2. 2Record the impact flag on the contact and skip user-level menu updates for that PSID.
  3. 3Fall back to the Page-level persistent menu, quick replies or buttons in messages for navigation.
  4. 4Re-probe occasionally rather than on every message; the call counts against the per-user rate limit.
  5. 5Log the fbtrace_id if impact appears on a large share of threads, since that suggests a wider issue to raise with Meta.

How to stop it recurring

Never make core navigation depend on a per-user menu. Build the Page-level menu so it works for everyone, and treat user-level overrides as an enhancement that can silently fail. Remember the per-user override budget of 10 calls per user per 10 minutes when probing. Menu limits are listed 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

Error 10 - quick answers

What does Messenger error 10 mean?

Code 10 with subcode 2018336 is unusual because Meta documents it as a diagnostic signal rather than as a mistake in your request. The error-codes table's entry reads simply "User Thread Impact," and the explanation is a test procedure: to determine whether there is user thread impact, call the user-level menu API. "If you get a valid response, there is no impact.

How do I fix Messenger error 10?

1. Probe with GET /me/custom_user_settings?psid=PSID; a valid response means no impact, 2018336 confirms it. 2. Record the impact flag on the contact and skip user-level menu updates for that PSID. 3. Fall back to the Page-level persistent menu, quick replies or buttons in messages for navigation. 4. Re-probe occasionally rather than on every message; the call counts against the per-user rate limit. 5. Log the fbtrace_id if impact appears on a large share of threads, since…

Should I retry after error 10?

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.