# Getting latest changesets stuck on "Saving changesets" status

**URL:** https://www.finalbuilder.com/forums/t/getting-latest-changesets-stuck-on-saving-changesets-status/6115
**Category:** Bugs
**Created:** [August 1, 2018, 12:46pm UTC](https://www.finalbuilder.com/forums/t/getting-latest-changesets-stuck-on-saving-changesets-status/6115 "2018-08-01T12:46:32Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![rogerwu](https://www.finalbuilder.com/forums/letter_avatar_proxy/v4/letter/r/7feea3/32.png) [@rogerwu](https://www.finalbuilder.com/forums/u/rogerwu)
#### Post date: [August 1, 2018, 12:46pm UTC](https://www.finalbuilder.com/forums/t/getting-latest-changesets-stuck-on-saving-changesets-status/6115/1 "2018-08-01T12:46:32Z")

</div>

Continua Version: 1.8.1.529  
  
Continua get stuck at "Saving changesets" when retrieving changes from a TFS Git repository. When this occurs on one repository, all subsequent checks on other repositories also become stuck at the "Saving changesets" status.

This also blocks all builds. Builds are added to the queue, but never start.

---

<div class="post-metadata">

### Author: ![Vincent](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/vincent/32/938_2.png) [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [August 1, 2018, 1:45am UTC](https://www.finalbuilder.com/forums/t/getting-latest-changesets-stuck-on-saving-changesets-status/6115/2 "2018-08-01T01:45:55Z")

</div>

My first suggestion would be to update to the latest 1.8.1.x build of Continua CI, as the build you are using is pretty old and there have been a lot of fixes for git since .529   
  
 [https://www.finalbuilder.com/downloads/continuaci/continuaci-version-history-v1.8.1](https://www.finalbuilder.com/downloads/continuaci/continuaci-version-history-v1.8.1)   
  
 If that doesn’t resolve this issue, then you will need to enable debug logging - [https://wiki.finalbuilder.com/display/continua/Debug+Logging](https://wiki.finalbuilder.com/display/continua/Debug+Logging) - and once the issue occurs again, stop the service and then send us the debug log. Be sure to turn off debug logging when done, as it does add some overhead to the server.   
  
 FWIW, in our experience, when git gets stuck like that, it’s usually due to it prompting for credentials.