I stumped on this the other day and thought it is interesting to share. If you have ever worked on any BIM360 (C4R) project, you should know by now that your local file resides on a hidden location other than your default Revit location.
From time to time, if you have sync issue between your local file with the central, you can run into issue where your local file gets corrupted. Autodesk has a KB article to walk you through the process of clearing out the local file. In this hidden location, your local C4R file does not resemble your actual file name; instead, it is named after some GUID number. In other words, you can't just find your corrupted local file and get rid of it. It takes some trial by error to clear out this folder when I first encounter this issue. From the KB, it tells you to open the journal file to determine the filepath of the damage model. I can tell you if you have never understand how to read a journal, this is going to be a tedious process. **You can however always clear everything inside the local cache but sometimes you can't afford to do so if you have a few projects working concurrently.**
The following tip might offer a quicker way to get to the damage model without opening the journal.
Reminder: You are doing this at your own risk!
In the event you have a corrupted local file. Go to Open --> file --> BIM 360, select your project hub folder and hit ENTER on your keyboard. Revit will prompt you with an error "BIM 360://your project hub name/......... File not found. Please verify the correct file name was given."
The one that starts with "{" and ends with "}" is the local file folder of your model.
Next, go to your window explorer and locate your user local data folder such as this:
%LOCALAPPDATA%\Autodesk\Revit\Autodesk Revit 20##\CollaborationCache
*Make sure you locate the correct Revit version.*
From there, your will see the same folder with the exact name ......
Go ahead to either move this folder out of this location or I normally just rename to a different name. Revit will then generate a "New" local file when you try to open the model again.
Hope this helps.
Happy syncing!