Messenger error 551: This person isn't available right now
Last verified against Meta for Developers - Messenger Platform error codes
This person isn't available right now.What error 551 means
Code 551 with subcode 1545041 is Messenger's way of saying the recipient exists, the Page can see them, but the platform will not deliver your message to them. Meta's error-codes table files the bare code 551 under "User Block Error: This person isn't receiving messages from you right now," and the subcoded variant carries the shorter string "This person isn't available right now." Both describe the same wall: something on the person's side of the conversation forbids delivery.
The most common reason is that the person blocked your Page or blocked messages from it. It also fires when the account has been deactivated or deleted, when the person has restricted who can message them, and in some cases when Messenger itself has limited the account. Crucially, Meta does not tell you which of these applies, deliberately: revealing whether a specific user blocked you would leak information about that person's choices. There is no API to check reachability in advance and no appeal path, because nothing is wrong with your app.
What is NOT wrong: your access token (the call authenticated fine), your permissions (the API got as far as the delivery check), the PSID (a wrong ID returns 100/2018001 instead), and the messaging window (window violations return code 10). A bot that treats 551 as a transient failure and retries is the classic mistake; every retry fails identically and inflates your error rate, which is itself a signal Meta watches.
In a support-bot context this error most often surfaces in drip or follow-up flows: the person chatted once, later blocked the Page, and your scheduled follow-up hits the wall. It is also the error you see when messaging users who tightened their privacy settings after Messenger's periodic privacy prompts. The narrative walkthrough of silent-bot causes, including this one, is in the Messenger bot troubleshooting guide.
What it looks like
{
"error": {
"message": "(#551) This person isn't available right now.",
"type": "OAuthException",
"code": 551,
"error_subcode": 1545041,
"fbtrace_id": "BLBz/WZt8dN"
}
}Why it happens
- The person blocked your Page, or blocked receiving messages from your Page specifically.
- The person deactivated or deleted their Facebook account after the conversation started.
- The person's privacy settings restrict who can message them, and your Page no longer qualifies.
- Messenger has restricted the recipient's account itself (spam checkpoints, memorialized accounts).
- A re-engagement campaign is replaying old PSIDs, some of whom have since opted out by blocking.
How to fix Messenger error 551
- 1Do not retry. The result is deterministic until the person unblocks the Page or reactivates their account, neither of which you can trigger.
- 2Mark the PSID as unreachable in your contact store and suppress it from every automated flow: drips, broadcasts, HUMAN_AGENT follow-ups.
- 3Distinguish it in your error handler from 100/2018001 (bad ID, a bug you can fix) and from 10-family window errors (timing, which the user can reset by replying).
- 4If a large share of your audience suddenly returns 551, check whether the Page has been restricted instead: test with a fresh test user, and review Page Quality in Meta Business Suite.
- 5Surface the failure to human agents in your inbox UI so they do not keep composing replies into a dead thread.
How to stop it recurring
You cannot prevent a person from blocking your Page, but you can stop the error from mattering. Record every 551 against the contact and gate all outbound automation on that flag. Keep re-engagement lists fresh: PSIDs older than a few months have a meaningfully higher block rate. And reduce the behavior that causes blocks in the first place, unwanted frequency and irrelevant broadcasts; the volume rules worth respecting are tabulated 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
- 551: User Block ErrorUser Block Error: This person isn't receiving messages from you right now.
- 200: Message Not Sent: person isn't availableMessage Not Sent: This person isn't available right now.
- 10: This person cannot receive messagesThis Person Cannot Receive Messages: This person isn't receiving messages from…
- 100: No matching user foundNo matching user found
- 9000001: Message deleted by the user or the businessThis Message has been deleted by the user or the business.
Error 551 - quick answers
What does Messenger error 551 mean?
Code 551 with subcode 1545041 is Messenger's way of saying the recipient exists, the Page can see them, but the platform will not deliver your message to them.
How do I fix Messenger error 551?
1. Do not retry. The result is deterministic until the person unblocks the Page or reactivates their account, neither of which you can trigger. 2. Mark the PSID as unreachable in your contact store and suppress it from every automated flow: drips, broadcasts, HUMAN_AGENT follow-ups. 3. Distinguish it in your error handler from 100/2018001 (bad ID, a bug you can fix) and from 10-family window errors (timing, which the user can reset by replying). 4. If a large share of your…
Should I retry after error 551?
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.