I posted this same question a little while back.
Received similar responses: see these articles...
Read through all posted "solutions". The only one that had any bearing on this situation was to perform an Audit on the central cloud model.
That worked... until someone that didn't have the latest service pack saved the model, then mine went back to showing the "error".
One additional thing that I have noticed is that not all borrowed elements or newly created worksets get released back to central after a sync.
There's some small change in how locals interact with Central cloud models in the latest update that is causing this but, it's easier to just say "make sure everyone's current" than it is to look into the issue and repair it so...
see the post from
@ennujozlagam : install the latest updates on everyone's machines. Including all of your consultants??? and ...
I have just decided to bite the bullet and perform a "Relinquish all mine" immediately after performing a sync.
-G
Gary J. Orr
GaryOrrMBI (MBI Companies 2014-Current)
aka (past user names):
Gary_J_Orr (GOMO Stuff 2008-2014);
OrrG (Forum Studio 2005-2008);
Gary J. Orr (LHB Inc 2002-2005);
Orr, Gary J. (Gossen Livingston 1997-2002)