IssueRaiser

[Down Time] Card throws 'maximum retries exceeded' error

Hi everyone, I see that all personal access tokens are currently failing, thus you will see the "Maximum retries exceeded" error. I'm looking into the issue to figure out what caused it. Ideally, it should be fixed in an hour when the PATs get rest. # Details ## Public instance information <img alt="Custom badge" src="https://img.shields.io/endpoint?url=https%3A%2F%2Fgithub-readme-stats-git-monitoring-github-readme-stats-team.vercel.app%2Fapi%2Fstatus%2Fup%3Ftype%3Dshields"> ## Explanation ------- Hey everyone, sorry for the recent downtimes. For the sake of transparency, we get a huge amount of requests per month (it's kind of mind boggling for a side project which I built just for fun). Here's the vercel dashboard statistics: ![image](https://user-images.githubusercontent.com/35374649/194407743-9af65825-483a-49af-9e16-cac3a5ea5a50.png) As you can see even with 73% of the responses being cached by vercel the amount of `live` requests are huge, and the bottleneck here is [Personal Access Tokens](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token) Each PAT have 5000 points, and based on the complexity of the GraphQL query & [resource limitations](https://docs.github.com/en/graphql/overview/resource-limitations) set by GitHub, it's actually very very low considering that amount of requests. To circumvent the issue, we currently have 7 PATs (thats 35k points) which sometimes get exhausted. Thanks t

Posted by anuraghazra on Nov 24, 2021, 6:03 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.3,000 issues0 comments

reliability (SaaS)

[Down Time] Card throws 'maximum retries exceeded' error

anuraghazraNov 24, 2021, 6:03 PM

Hi everyone, I see that all personal access tokens are currently failing, thus you will see the "Maximum retries exceeded" error. I'm looking into the issue to figure out what caused it. Ideally, it should be fixed in an hour when the PATs get rest. # Details ## Public instance information <img alt="Custom badge" src="https://img.shields.io/endpoint?url=https%3A%2F%2Fgithub-readme-stats-git-monitoring-github-readme-stats-team.vercel.app%2Fapi%2Fstatus%2Fup%3Ftype%3Dshields"> ## Explanation ------- Hey everyone, sorry for the recent downtimes. For the sake of transparency, we get a huge amount of requests per month (it's kind of mind boggling for a side project which I built just for fun). Here's the vercel dashboard statistics: ![image](https://user-images.githubusercontent.com/35374649/194407743-9af65825-483a-49af-9e16-cac3a5ea5a50.png) As you can see even with 73% of the responses being cached by vercel the amount of `live` requests are huge, and the bottleneck here is [Personal Access Tokens](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token) Each PAT have 5000 points, and based on the complexity of the GraphQL query & [resource limitations](https://docs.github.com/en/graphql/overview/resource-limitations) set by GitHub, it's actually very very low considering that amount of requests. To circumvent the issue, we currently have 7 PATs (thats 35k points) which sometimes get exhausted. Thanks t

Comments (0)

No comments yet. Start the discussion.

Comment on this issue