Messenger Platform · error code

Messenger error 2018234: Secondary receiver cannot see other secondary receivers

Permanent - do not retryPermissions, app review & thread control

Last verified against Meta for Developers - Messenger Platform error codes

What Messenger returns
Denying visibility of any secondary receiver to another secondary receiver other than itself.

What error 2018234 means

Code 2018234 is a privacy rule from the handover protocol: "Denying visibility of any secondary receiver to another secondary receiver other than itself." Under that model, apps attached to a Page as Secondary Receivers could participate in thread control but were not allowed to discover each other. When a Secondary Receiver asked for information about the other receivers, the platform refused and returned this error. It could see itself, nothing more.

The usual reason an app makes that request is to find a target_app_id for pass_thread_control, for example a bot that wants to hand the person to a live-chat tool. The design expects that ID to come from configuration, not discovery, because one vendor's app should not be able to enumerate the other vendors installed on a customer's Page.

Meta has moved Messenger to Conversation Routing, which keeps most handover APIs compatible. The rule this error expresses still makes sense in that world: treat the list of other apps on a Page as information the Page owner gives you, not something you query.

What it looks like

{
  "error": {
    "message": "(#2018234) Denying visibility of any secondary receiver to another secondary receiver other than itself.",
    "type": "OAuthException",
    "code": 2018234,
    "fbtrace_id": "BLBz/WZt8dN"
  }
}

Why it happens

  • A non-primary app requesting the list of secondary receivers for the Page.
  • Auto-discovery code that tries to find a live-agent app's ID at runtime.
  • Generic admin tooling that queries routing configuration with a helper app's token.

How to fix Messenger error 2018234

  1. 1Stop querying other receivers from a helper app; the call will keep failing.
  2. 2Collect the target app ID from the Page admin during setup and store it in configuration.
  3. 3Use pass_thread_control with the configured target_app_id, or omit it where the routing setup supports passing back to the default app.
  4. 4Use GET /PAGE-ID/thread_owner when you only need to know who owns a conversation.

How to stop it recurring

Make routing configuration explicit: an admin enters which app receives handoffs, and your app validates it with a test pass during onboarding. Keep thread ownership checks to the thread_owner endpoint and messaging_handovers webhooks, which every connected app may use, and re-check the stored target whenever the Page adds or removes an app.

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

Related codes

Error 2018234 - quick answers

What does Messenger error 2018234 mean?

Code 2018234 is a privacy rule from the handover protocol: "Denying visibility of any secondary receiver to another secondary receiver other than itself." Under that model, apps attached to a Page as Secondary Receivers could participate in thread control but were not allowed to discover each other.

How do I fix Messenger error 2018234?

1. Stop querying other receivers from a helper app; the call will keep failing. 2. Collect the target app ID from the Page admin during setup and store it in configuration. 3. Use pass_thread_control with the configured target_app_id, or omit it where the routing setup supports passing back to the default app. 4. Use GET /PAGE-ID/thread_owner when you only need to know who owns a conversation.

Should I retry after error 2018234?

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.