Messenger Platform · error code

Messenger error 100: Cannot send both message and state

ConfigurationGeneric & request errors

Last verified against Meta for Developers - Messenger Platform error codes

What Messenger returns
Cannot send both message and state at the same time.

What error 100 means

Code 100 with subcode 2018014 means one Send API request carried both a message object and a sender_action. The "state" in Meta's wording is the sender action: typing_on, typing_off, mark_seen, or a reaction. The sender actions guide is explicit that requests displaying a sender action "should only include the sender_action parameter and the recipient object," and that text, templates and every other Send API property go in a separate request.

It usually appears when someone adds a typing indicator to an existing send helper by merging one more field into the payload. The request is well formed JSON and the token is fine; the platform simply refuses to interpret a body that asks for two different things at once, and neither the message nor the indicator is delivered.

It is purely a request-shape problem. It is unrelated to the 24-hour window, permissions, or the recipient's state, so no amount of waiting or re-authorizing changes the outcome.

What it looks like

{
  "error": {
    "message": "(#100) Cannot send both message and state at the same time.",
    "type": "OAuthException",
    "code": 100,
    "error_subcode": 2018014,
    "fbtrace_id": "BLBz/WZt8dN"
  }
}

Why it happens

  • A send helper that merges sender_action into the same body as message.
  • Framework middleware that adds typing_on to every outgoing payload automatically.
  • Reaction requests (sender_action react) built on top of a message payload template.
  • Copy-pasted examples that combined fields from different documentation snippets.

How to fix Messenger error 100

  1. 1Split the call: POST recipient plus sender_action first, then POST recipient plus message.
  2. 2Strip message, messaging_type and tag from any request that carries sender_action.
  3. 3Keep typing_on and typing_off in separate requests too; Meta notes that batched indicators may flash for only a fraction of a second.
  4. 4Add a guard in your API client that rejects bodies containing both keys before they reach Meta.
  5. 5Re-send the original message once the request is corrected.

How to stop it recurring

Model sender actions and messages as two distinct functions in your client library, so it is impossible to build a combined body. A unit test that asserts no payload contains both message and sender_action catches regressions cheaply. Typing indicator behavior is 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 100 - quick answers

What does Messenger error 100 mean?

Code 100 with subcode 2018014 means one Send API request carried both a message object and a sender_action . The "state" in Meta's wording is the sender action: typing_on , typing_off , mark_seen , or a reaction.

How do I fix Messenger error 100?

1. Split the call: POST recipient plus sender_action first, then POST recipient plus message. 2. Strip message, messaging_type and tag from any request that carries sender_action. 3. Keep typing_on and typing_off in separate requests too; Meta notes that batched indicators may flash for only a fraction of a second. 4. Add a guard in your API client that rejects bodies containing both keys before they reach Meta. 5. Re-send the original message once the request is corrected.

Stop debugging Messenger by hand

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