Messenger error 551: User Block Error

Bare code 551 is the Messenger Platform's user-block error, listed in Meta's table as "User Block Error: This person isn't receiving messages from you right now." It is the same family as the subcoded 551/1545041: the recipient exists and your request was valid, but delivery to this person is refused because of a condition on their side, a block of your Page, messages from Pages turned off, a deactivated account, or an account-level restriction.

Meta deliberately keeps the wording vague. Confirming that a specific person blocked your Page would disclose that person's private choices, so the platform folds all recipient-side refusals into one string and gives you no way to distinguish or verify them. There is no pre-flight reachability check, no appeal, and no fix from the sender's side; the state changes only if the person unblocks the Page, reactivates their account, or messages you again, and that last event is the only signal you will actually observe, as a normal inbound webhook.

For a production bot, 551's importance is statistical. Individual occurrences are routine; a rising 551 rate across your audience is one of the clearest signs your messaging is unwelcome, too frequent, too promotional, or aimed at stale lists, and it is exactly the signal that precedes Page-level enforcement like 368. Track it as a health metric, not just an error.

{
  "error": {
    "message": "(#551) This person isn't receiving messages from you right now.",
    "type": "OAuthException",
    "code": 551,
    "fbtrace_id": "BLBz/WZt8dN"
  }
}

Earn the inbox: frequency caps per recipient, content that answers rather than sells, and prompt suppression of unengaged contacts keep block rates low. Treat every 551 as feedback and every 551 trend as a product review. The recipient-side refusal family and how to tell it apart from ID bugs and window errors is mapped in the Messenger troubleshooting guide, with volume rules in the limits reference.