Json O365-如何更好地理解和处理429节流响应

呼叫Office 365时，可能会发生各种限制响应

以下是一些例子：

状态代码429：

{
"error": {
    "code": "activityLimitReached",
    "innererror": { "code": "throttledRequest" },
    "message": "The request has been throttled",
    "retryAfterSeconds": 0
}

{
  "error": {
    "code": "activityLimitReached",
    "message": "The application or user has been throttled."
  }
}

Message [429 TOO MANY REQUESTS]]

状态代码429：

{
"error": {
    "code": "activityLimitReached",
    "innererror": { "code": "throttledRequest" },
    "message": "The request has been throttled",
    "retryAfterSeconds": 0
}

{
  "error": {
    "code": "activityLimitReached",
    "message": "The application or user has been throttled."
  }
}

Message [429 TOO MANY REQUESTS]]

状态代码429：

{
"error": {
    "code": "activityLimitReached",
    "innererror": { "code": "throttledRequest" },
    "message": "The request has been throttled",
    "retryAfterSeconds": 0
}

{
  "error": {
    "code": "activityLimitReached",
    "message": "The application or user has been throttled."
  }
}

Message [429 TOO MANY REQUESTS]]

我怀疑这些被限制的消息中的每一条实际上都可能指向不同的状态

这些信息实际上意味着不同的事情吗

重试后

标题值始终为

120

。总是。我们应该做指数退避吗

有关限制的SharePoint文档提到添加一个特殊的用户代理标题。这会对调用Microsoft Graph产生影响吗

---

不同的端点/服务有自己的限制规则。一些节流阀基于并发请求，通过10分钟窗口内的请求数，等等

有关如何使用MicrosoftGraph进行节流的详细信息，以及处理

429

消息的提示，我建议阅读