resolve renegade status

[josebrwn]

frequently when using vault the files that I have checked out will suddenly appear as renegade. this seems to happen when I've rebooted, or my computer's gone to sleep, inadvertently opened two instances of the vault client.

in these circumstances vault changes the status of these files from checked out & edited to renegade & checked out. It won't let me check them in and I can't figure out how to resolve their status without undoing checkout and getting latest, which creates a risk of losing my work.

is there a reliable means to force the renegade status to resolve itself without having to take unusual pains to ensure that Vault does not overwrite my work?

I'm running v. 5.0.4 on windows 7 and I have searched the forum already.

[lbauer]

Renegade status means Vault Client thinks the file has been modified, but the file is not checked out.

Vault determines the status of file by comparing the file (or its timestamp) to the last baseline, which is the last time the file was retrieved to the working directory. Baselines can be stored in the working directory or in the user's local profile in App Data or Local Settings, depending on your OS.

I'm not sure what set of circumstances is causing your files to be renegade AND checked out. Are you logging in as the same Vault user? Are you logging in under the same Windows account? Baselines and client cache are unique to each Vault and Windows user.

Some options to set things right -- you can try undoing the checkout, using the Leave option. That will leave the modified file on disk. Another option would be to undo the checkout from the Vault Admin Web Client. This setting is in the Admin Web Client under Source Control Repositories->(Repository name)->Undo Checkout.

[baklazanek]

This setting is in the Admin Web Client under Source Control Repositories->(Repository name)->Undo Checkout.

HURRAY!

It's working

[lbauer]

Glad that helped you!