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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


POSTs to /pullrequests results in 504/timeouts


(UPDATE: Atlassian have opened for this issue. Only seems to happen when a PR is opened with no changes to merge into the destination branch): 

"Creating an empty pull request via API 2.0 endpoint currently hangs with a 504 gateway error."

Hi folks, 

We are seeing 504s/timeouts for POSTs to /pullrequests API over the weekend and today. May be effecting other APIs but not sure.

Is this known or has access to this and similar APIs changed(maybe via whitelisting etc)?

b'<html>\r\n<head><title>504 Gateway Time-out</title></head>\r\n<body>\r\n<center><h1>504 Gateway Time-out</h1></center>\r\n</body>\r\n</html>\r\n'

Status page at the time of writing looks green 




4 answers

1 accepted

2 votes
Answer accepted

Raised support ticket(I didnt realise that was an option!): (may not be visible to everyone)

Thanks @peter - we're unable to submit tickets because we're on the free tier. Would love to know what they say! (can't see the ticket, I believe it's private to you and support)

Yeah, they opened a bug with development team. That ticket can be found here: 

Like # people like this

This seems to be working for me now, at least POSTs to the pullrequests API is working again. 

Scratch that, maybe only worked because my PR had changes to merge into the destination branch.

I was made aware of a new bug by Karthick S:

I also suspect you might be impacted by a bug that is related to the creation of an empty pull request through the API 2.0 endpoint, which crashes with the gateway error 504. That is when trying to create a pull request which has no changes, instead of receiving a message saying "There are no changes. The source and destination are the same.", error 504 is occurring.

We already have an open bug with our development team. You can track this bug through this link BCLOUD-22009.

We have been experiencing this same issue since Friday with POST requests. We already tested GET requests and those are working fine. Any help on this would be appreciated.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events