I have subscribed for 'repo:push' notifications, and have found that the associated endpoint is hit multiple times when this occurs.
When I receive the notification I am processing a file and uploading to an AWS s3 bucket, then returning a 200 response.
I suspect that the notification requires an acknowledgement in a certain amount of time, and I am not responding quickly enough, thus the 2nd, and sometimes 3rd, 'X-Attempt-Number'.
Can someone clarify if my assumption is correct? Is there a way to adjust the timeout for the notification response? Is there a standard way of handling these notifications?
Hi @Corey Malcom ,
Bitbucket expects the response to a request within 10 seconds. If there is no response after 10 seconds, the request will timeout and Bitbucket will resend the request up to two more times. (This is documented here)
I'm afraid that we cannot adjust the timeout, the suggestion mentioned in the documentation I linked is:
To avoid timeouts, you can acknowledge receipt of the request by replying with an appropriate response before doing any expensive processing on your end.
Please feel free to let me know if you have any questions.
Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events