The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
× Create
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Community resources
Community resources
Community resources
BitBucket: changes made via REST API calls are eventually consistent
neomatrix369
June 25, 2019 edited
What is the recommended practise when using the REST API calls, I have noticed any mutations to the repo are reflected only after a short delay, this delay differs each time.
What I mean by that is if I close an existing pull request and then create a new one via the REST API calls, and then if I immediately request for a list of Pull Requests, I don't see the newly created PR appear in the results till say after 5 to 15 seconds (varies).
I guess returning a future and then resolving the future is the way forward, any examples of how others have done this? Or any examples from Atlassian itself?
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.
Copyright © 2026 Atlassian