Building with SCM causes a filesystem out of sync error

 The out of sync problem occurs when a workspace has been loaded into different locations.  If the repository side version of the workspace has been altered by one copy of the physical sandbox version of the workspace by a deliver, then all other instances of the physical sandboxes will be out of sync.  The different instances of the sandbox could be caused by copying the sandbox files to another location, or loading different components to different locations, so long as the .jazz5 metadata for the loaded folder points back to the same repository workspace.  To avoid the issue, if you find you need different instances of the same source, make new dedicated repository workspace for each instance.  This avoids potential collisions over out of sync data.