Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,455,378
Community Members
 
Community Events
175
Community Groups

Error 429 - Too many requests

I have a user repeatedly receiving this error when trying to review tickets in Jira Cloud.  He has no other background processes running within Jira.  I submitted a ticket to Atlassian back in April and have escalated as far as it will let me but they just promise that they are monitoring it and then nothing ever changes.  It's been 2 months now and it happened twice yesterday and once today, sometimes when he is showing his screen to clients.  Has anyone else experienced this and found a solution?  

The error reads:   Something went wrong.  Try reloading the page, then check our statuspage for any current outages.  If there are no relevant outages, create a support request so we can help you out.  If you create a request, include the following so we can help you as fast as possible:  Error type:  429 - Too many requests; log reference: d7c955ac-34a1-43c7-a645-3ebd2ab10ce.

2 answers

I have the same issue. Creating a ticket now

Hello Team, any solutions ..?

After a few months of investigation, the support team seems to have resolved it.  Not sure what exactly was causing the problem.

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events