Thanks god that an archive was written shortly before this happened.
Have any of you ever had something like this and any ideas on how to fix it, if no archive has been written?
We could no longer access the project, either from a fresh project or from another workstation.
I read the post from 2021, but it wasn’t helpful. That’s why I added the Flame version in the title.
FYI: I have blacked out the IP and the project name.
The warning box defines the path to the corrupted workspace.
Look inside the same directory for automatically generated backups.
Rename the corrupted file and move it to somewhere else (/var/tmp).
It’s been forever since I had to do this and I’m not in front of a workstation, but tar extract or unzip or just rename the last good backup and restart flame.
If it doesn’t immediately work keep stepping back in time until you isolate the last good backup and your project will magically re appear.
thanks for the answer we will definitely try it out!
Wow. Fortunately I haven’t had that problem of corrupted desktops for a long time. First time I see that warning window. It seems perform the classic fix described by Phill, automatically.
@philm
I tried it today and it worked. Thank you
Would be nice to know what happened before you go to this state. We have not seen corrupted data in ages. But if the workstation has been shutdown in the middle of an operation or if the file system is corrupted (failing SSD these days happens) this might happen. We generate backups so you can always go back in time and save life 
