不明白“(#4)达到用户请求限制”
{
"error": {
"message": "(#4) User request limit reached",
"type": "OAuthException"
}
}
我不确定这个错误的原因，是的，我已经做了很多搜索类似的用户问题（它们是错误＃17，或达到应用程序限制）。我是在常规图形 API 调用（例如 https://graph.facebook.com/me ）上执行此操作，而不是必然是 FQL，就像其他人遇到的那样。
达到用户请求限制使它看起来像是每个用户的限制，但根据http://www.fb-developers.info/tech/fb_dev/faq/general/gen_10.php ，#4 为 “已达到应用程序请求限制“ 和#17 是“已达到用户请求限制”。
我不相信我会达到 1 亿/天的应用程序限制。我只获得几个用户的身份验证令牌，因此这不是我收到的应用程序范围的错误消息。当我请求太快时，通常会收到 FQL_EC_RATE_LIMIT_EXCEEDED。
但对于出现上述错误“(#4) User request limit returned”的那两个用户，我已暂时将他们列入加载数据的黑名单，但他们仍然得到当我一天后尝试使用该身份验证令牌访问时出现上述错误。
所以总而言之......
当该用户的身份验证令牌未用于 24 中的任何查询时，我不明白如何获得“（#4）已达到用户请求限制” - 小时前。而且我不知道这些用户有什么特别之处。
任何意见或建议将不胜感激。几天前只有一个用户，但今天第二个用户开始遇到这个问题，我担心这个问题在未来会变得更糟，而且没有明确的解决方案。
{
"error": {
"message": "(#4) User request limit reached",
"type": "OAuthException"
}
}
I'm not sure the cause of this error, and yes I've done lots of searching around for similar user's problems (they are error #17, or app limit reached). And I'm doing this on regular graph API calls (such as https://graph.facebook.com/me ), not necessarily FQL like others have run into.
User request limit reached makes it seem like a per-user limit, but according to http://www.fb-developers.info/tech/fb_dev/faq/general/gen_10.php , #4 is "Application request limit reached" and #17 is "User request limit reached".
I don't believe there's anyway I'm hitting the 100M/day app limit. And I only get it for a couple users' auth tokens, so it's not an app-wide error message I'm getting. And when I request too quickly, I usually get FQL_EC_RATE_LIMIT_EXCEEDED.
But for those two users with the above error "(#4) User request limit reached", I've temporarily blacklisted them from loading data, but yet they still get the above error when I try to access using that auth token a day later.
So in conclusion...
I don't understand how I can get "(#4) User request limit reached" when the auth-token for that user is not being used for any queries in a 24-hour period prior. And I don't know what is special about these users.
Any advice or suggestions would be greatly appreciated. It was only one user a few days ago, but today a second user started running into this problem, and I'm worried the problem will just get worse in the future with no clear resolution.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
以下是错误代码列表： http://fbdevwiki.com/wiki/Error_codes
#4 表示您发出了太多 API 请求。在一定时间内，您的申请可以提交的数量是有限制的。每个用户也有限制。如果您等待一段时间，错误应该会清除并允许您再次发出请求。
错误代码是旧 API 的回溯，因此它们可能只是将 #4 和 #17 组合起来，始终只返回 #4。
此外，限制并不固定，例如“100M/天”。转到您的应用程序的见解并在诊断下查看。它将向您显示哪些请求导致了该错误。这些限制每天都在变化，我认为这与其他流量的多少有关。
Here is a list of error codes: http://fbdevwiki.com/wiki/Error_codes
#4 means you've made too many API requests. There are limits on how many your application can make given a certain amount of time. There are also limits based on each user. If you wait for a while the error should clear and allow you to make requests again.
The error codes are a throwback from older API's so it's possible they just combined #4 and #17 to always just return #4.
Also, the limits are not fixed such as "100M/day". Go to Insights for your application and look under Diagnostics. It will show you what requests are causing that error. The limits vary from day to day and I think are related to how much other traffic there is.