There have multiple instances where the API sends back an error response, stating "Too Many Requests", "Not Found", "Service Unavailable", "Bad Request". This error repetition has significantly increased in October 2020. Following are the examples.
Response: StatusCode: 404, ReasonPhrase: 'Not Found', Version: 1.1, Content: System.Net.Http.StreamContent, Headers: { Connection: keep-alive RCRequestId: 43a61904-1dc1-11eb-8f8a-0050568d56ad RoutingKey: IAD01P13PAS06 X-Rate-Limit-Group: medi
Response: StatusCode: 429, ReasonPhrase: 'Too Many Requests', Version: 1.1, Content: System.Net.Http.StreamContent, Headers: { Connection: keep-alive X-Application-Context: application:8080 X-Rate-Limit-Limit: 5 X-Rate-Limit-Window: 60 X-R
Response: StatusCode: 503, ReasonPhrase: 'Service Unavailable', Version: 1.1, Content: System.Net.Http.StreamContent, Headers: { Connection: keep-alive X-Application-Context: application:8080 Retry-After: 40 RCRequestId: be75562a-ebcd-11ea-ad
Response: StatusCode: 400, ReasonPhrase: 'Bad Request', Version: 1.1, Content: System.Net.Http.StreamContent, Headers: { Connection: keep-alive RCRequestId: 366eb026-0bb4-11eb-b8a3-0050568db9e8 RoutingKey: SJC01P13PAS07 X-Rate-Limit-Group: he
So what is your exact question? Do you want to know the reason behind these errors?
429 'Too Many Requests' is due to the violation of Rate limit applied on the API. You need to check the rate limit plan applied on your API.
503 'Service Unavailable' is due to some temporary issue with the server, some temporary outage or server down issue.
400 'Bad Request' is due to the improper request fed in the API called. if the API request is not as per the API format defined, you may get this error.
If you want to check why these error has increased after a specific date, you can either debug checking logs or you can request the backend Dev support team to investigate and ask their help.
If you have a production account, you can raise a support request with them asking help to investigate the issue
Yes, would like to know the reason behind an increase in these errors. I have already raised a ticket and posted a query on the developer forum as well. I haven't received any updates on the developer forum question.
Following is an example of the "Purged" incoming fax. Time is in UTC.
2020-11-04 03:26:19.053
{
"uuid":"1219366765209121432",
"event":"/restapi/v1.0/account/334268009/extension/277890029/fax?direction=Inbound",
"timestamp":"2020-11-04T03:26:16.328Z",
"subscriptionId":"c73ed71d-61d5-4aa9-aea3-93ffb4123766",
"ownerId":"334268009",
"body":{
"uri":"https://api.ringcentral.com/restapi/v1.0/account/334268009/extension/277890029/message-store/1379138253028",
"id":1379138253028,
"type":"Fax",
"availability":"Purged"
}
}
A new Community is coming to RingCentral!
Posts are currently read-only as we transition into our new platform.We thank you for your patience
during this downtime.
Try Workflow Builder
Did you know you can easily automate tasks like responding to SMS, team messages, and more? Plus it's included with RingCentral Video and RingEX plans!Try RingCentral Workflow Builder
