All geek questions in one place

551 with Facebook Messenger bot - “This person is not available right now”

I wrote a simple bot for Facebook Messenger that accepts user text, applies a simple conversion, and immediately returns the result.

When testing, I myself never encountered a problem, but it seems that for some users, Facebook returns the following error when the converted message is sent back (from my server logs):

"www-authenticate": "OAuth \" Facebook platform \ "\" invalid_request \ "\" (# 551) This person is not available right now. \ ""

Any ideas what would be the reason for this? It seems that random users randomly happen, and users should be available, as the result is returned immediately.

Thanks!

+5
source share
2 answers

This is currently a confirmed bug on the Facebook platform. Place of error: https://developers.facebook.com/bugs/465154327166499/ (as @ m90 mentioned, it requires a Facebook developer account to view it).

Description of the error and steps to reproduce:

  • You have a new Facebook user (who has not previously interacted with your application)
  • With this user, specify everything that usually produces an automatic response from the application.

Expected Result: Bot should respond

Actual result: For applications in development mode, this is error code 551 as follows:

{"error":{"message":"(#551) This person isn't available right now.","type":"OAuthException","code":551,"error_subcode":1545041, ...

For applications in production mode (already submitted and publicly available), this is a 200 error:

 {"error":{"message":"(#200) This person isn't available right now.","type":"OAuthException","code":200,"error_subcode":1545041,...

Note: if the user sends more messages, the bot starts to respond normally after the second message from the same user.

Based on the information on the Facebook platform error page, the error appeared at the end of May 2017. On our side, we notice this last week (starting on June 5), it is important to note that new applications also crash due to this problem.

UPDATE June 9, 2017. The error is marked as fixed and is working on our side now. If you still have problems, Facebook asks you to comment on the error page.

+3
source

I have the same error. This was due to the fact that my page was not published. When I posted the Facebook page, this error disappeared.

+1
source

Source: https://habr.com/ru/post/1268573/

More articles:


All Articles