Why are old versions loaded when no one else uses the file?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Vault loads random versions instead of the latest version for no reason.
Simple as I can put it. For example, I am working on an assembly on Friday, making a bunch of changes to the sub-components and the assembly. Then I save and check in to pick up the work on Monday morning. When I load the file on Monday the assembly and a few of the sub-components are red dot- newer version in vault. This confuses and concerns me because we have a large, multi-location team and its possible for another team member to change the parts, and not notify or consider my work at all. I go through the work of pulling up each of the sub-components to check the history and I see "Local Same As: older version" instead of the latest version.
I realize that all I have to do is refresh the files, but it causes wasted time as I am not sure if my design was altered or not, so I have to verify.
Does anyone know why this happens?? I am not satisfied with "just refresh the file and it will be fine" because it may not be, so it's creating a lot of wasted time. I also want to understand why this happens and maybe prevent it from happening.