skip to Main Content

I have a peculiar issue with the Facebook API. I think it probably has to do with high volume, but that has not brought me any closer to the solution. When posting out messages to Facebook API, I occasionally receive an error such as:

HTTP/1.1 100 Continue
Date: Sat, 17 Dec 2016 19:22:38 GMT

HTTP/1.1 500 Internal Server Error
Access-Control-Allow-Origin: *
Pragma: no-cache
Cache-Control: private, no-cache, no-store, must-revalidate
facebook-api-version: v2.3
Expires: Sat, 01 Jan 2000 00:00:00 GMT
x-fb-trace-id: El4BfeJo4vI
x-fb-rev: 2746767
Content-Type: text/html
X-FB-Debug: F3xHF4IY15E3VK9M5acge9B6jBKOEqwP2Ob4F8WsoYRkGeAiY2PkzOjiiawhQ/Uq0TT/Xen+JLZtFXA9ZUsbRg==
Date: Sat, 17 Dec 2016 19:23:08 GMT
Connection: keep-alive
Content-Length: 77

{"error":{"code":1,"message":"An unknown error occurred","error_subcode":99}}

Usually retries later will work for the same request so it would not appear to be the culprit. The issue here, however, is that the message still sometimes appears to go through. How should such responses be handled?

I read on the Continue header, but I’m none the wiser now – especially since it comes with a non-descriptive 500 Internal Server error.

4

Answers


  1. It has been reported several times that a too long request will result in this type of error-subcodes (99). Try to narrow your request parameters while Facebook doesn’t support long requests. (Although the 500 error looks new to me.)

    Login or Signup to reply.
  2. You can probably safely ignore the 100 header; it’s correctly been followed up as you have another response (the 500).

    You should never really get a a 500 from any site: means their code is broken. Should report it here: https://developers.facebook.com/bugs/

    Login or Signup to reply.
  3. fb-reply

    “An unknown error occurred”,”code”:1,”error_subcode”:99″

    Reason for above error according to facebook:

    This error code is an indication that your request timed out. It may be the case that the request is valid, however the maximum processing time for the API was exceeded. Recommendation: Wait a few minutes, and then try again. If the problem persists, please continue filing a bug report.

    Login or Signup to reply.
Please signup or login to give your own answer.
Back To Top
Search