Thanks for taking the time to reply. I've been using that and other work-arounds, but it still takes a bite out of a typical day of development. I'll probably have to try some sort of comparative analysis on the two projects. It's hard to find time for such things and there's no guarantee that I'll be successful.
If you are saving to a remote server, make sure the server timeclock is correct.
If you are using VMWare, and saving to your host machine, make sure time synchronization is enabled.
Make sure there is not a dependency in the second project to a file in the first project, which may be updated as the build finishes on the first project.
You could possibly open 2 instances of PSoC Creator and keep 1 project in each.
Of course, for PSoC 6, that would not be advisable.
Thanks for the response. None of those conditions exist.
The behavior persists regardless of the PC used and the one project behaves, while the other does not.
The projects have a distant common ancestor.
I can't remember for sure, but I think the problem started when we migrated the project to PSoC Creator 4.because I remember everyone wanting to go back to the older version of PSoC Creator.