Messenger Platform · error code

Messenger error 2018144: Instant Game notification limit reached

RetryableRate limits & throttling

Last verified against Meta for Developers - Messenger Platform error codes

What Messenger returns
Could not send Instant Game message to the user at this time, only 5 notifications can be sent to a user within 10 days since they last played.

What error 2018144 means

Code 2018144 applies to Pages connected to Facebook Instant Games, where the game's bot can message players to bring them back. The message states the rule in full: "Could not send Instant Game message to the user at this time, only 5 notifications can be sent to a user within 10 days since they last played." Meta's suggested fix is equally direct: pause your requests until the number of requests falls below the limit.

The important detail is the anchor point. The budget is counted from the player's last play session, not from the first notification and not on a rolling calendar. When the person plays again, the clock resets. When they do not, you get five sends to win them back and then the channel closes for that player until they return to the game.

This is per player, so other players keep receiving messages normally. It is not a block (551), not a Page restriction, and not a global rate limit like 613. Instant Game Pages also have other quirks, such as the User Profile API not working for their PSIDs, which surfaces as plain code 10.

What it looks like

{
  "error": {
    "message": "(#2018144) Could not send Instant Game message to the user at this time, only 5 notifications can be sent to a user within 10 days since they last played.",
    "type": "OAuthException",
    "code": 2018144,
    "fbtrace_id": "BLBz/WZt8dN"
  }
}

Why it happens

  • A re-engagement sequence with more than five steps for lapsed players.
  • Several notification types (rewards, events, reminders) each sent independently to the same player.
  • Retrying failed notifications, which spends budget on repeats.
  • No record of when the player last played, so the scheduler cannot tell where the budget stands.

How to fix Messenger error 2018144

  1. 1Stop sending to that player and drop queued notifications for them.
  2. 2Record the last-play timestamp and a per-player count of notifications sent since then.
  3. 3Cap your re-engagement sequence at five messages and spread them across the 10 days.
  4. 4Resume only after the player plays again, which resets the window.

How to stop it recurring

Plan the lapsed-player sequence around the budget: pick the five messages most likely to bring someone back and merge minor events into them. Keep the counter next to the last-play timestamp so every sender checks it before calling the Send API.

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

Related codes

Error 2018144 - quick answers

What does Messenger error 2018144 mean?

Code 2018144 applies to Pages connected to Facebook Instant Games, where the game's bot can message players to bring them back.

How do I fix Messenger error 2018144?

1. Stop sending to that player and drop queued notifications for them. 2. Record the last-play timestamp and a per-player count of notifications sent since then. 3. Cap your re-engagement sequence at five messages and spread them across the 10 days. 4. Resume only after the player plays again, which resets the window.

Can I retry after error 2018144?

Yes - this is a retryable condition. Back off (start around one second and double on each attempt, with jitter) and watch for a retry-after hint from the platform before resending.

Stop debugging Messenger by hand

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