已达到Facebook应用请求限制 [英] Facebook Application Request limit reached

问题描述

我收到FBerror此操作无法完成：已达到应用程序请求限制。有人知道为什么会这样吗？如何检查限制？如何增加限制？什么取决于限制分配？

解决方案

我最近遇到这个问题，使用应用程序访问令牌进行大量请求最初的项目要求要求用户不必授权该应用程序）。

在很多挫折之后，我们终于和Facebook的联系人保持联系以下信息是针对我关于请求限制的问题：

有一个限制，但是相当高，应该很难打除非它们对所有呼叫使用相同的访问令牌，而不是缓存结果等。每个访问令牌每600秒有600个呼叫。

最终，我们最终要求用户授权，因为Facebook在计算其中时似乎不区分用户访问令牌（每个用户一个令牌）和应用程序访问令牌（所有用户的一个令牌）看到如果您遇到用户访问令牌的错误，您可能需要优化您的API调用（可能通过组合FQL查询或替换多个请求限制）使用单个FQL查询图表请求）。

I am getting an FBerror "This operation can't be completed: Application request limit reached". Does anybody know why is it so? How to check the limit? How to increase the limit? What depends on the limit allocation?

解决方案

I recently ran across this issue doing a large number of requests using an application access token (the initial project requirements mandated that the user shouldn't have to authorize the app).

After much frustration, we finally were put in touch with a contact at Facebook who provided the following info in response to my question regarding request limits:

There is a limit, but it's pretty high, it should be difficult to hit unless they're using the same access tokens for all calls and not caching results, etc. It's 600 calls per 600 seconds per access token.

Ultimately we ended up requiring the user to authorize, as Facebook does not seem to distinguish between user access tokens (one token per user) and application access tokens (one token for all users) when calculating its seemingly arbitrary request limits.

If you are running into this error with a user access token, you may need to optimize your API calls (possibly by combining FQL queries or replacing multiple Graph requests with a single FQL query).

这篇关于已达到Facebook应用请求限制的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！