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

POSTs to /pullrequests results in 504/timeouts

Peter July 11, 2022

(UPDATE: Atlassian have opened https://jira.atlassian.com/browse/BCLOUD-22009 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 https://bitbucket.status.atlassian.com/ 

 

Thanks!

Peter 

4 answers

1 accepted

2 votes
Answer accepted
Peter July 12, 2022

Raised support ticket(I didnt realise that was an option!): 

https://support.atlassian.com/requests/BBS-188867 (may not be visible to everyone)

Mike July 12, 2022

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)

Peter July 13, 2022

Yeah, they opened a bug with development team. That ticket can be found here: https://jira.atlassian.com/browse/BCLOUD-22009 

Like # people like this
0 votes
Peter July 12, 2022

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

Peter July 13, 2022

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.

0 votes
Mike July 11, 2022
0 votes
Renato July 11, 2022

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
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events