Network problems happen all the time, and with ressources in the cloud, mapped drives, vpn connections, home office etc. are more likely to happen nowadays than in history when it was sufficient to plug in just the one network cable.
This idea is to make Creo resilient regarding network connection interruptions.
Right now I am looking at a Creo instance that has frozen last evening just because a vpn connection dropped for a while. Everything is restored now and every other application was able to continue working from the state as it was before. Creo is still frozen. It will never get back to a usable state - as far as I can tell from previous experience - so I will again lose the work that was made between saving last time and the random network problem that occured.
One possible reply to this could of course be 'fix your network problems first' - but what should I fix first if the problem does not occur because of my action or decisions like DSL line hickups, vpn reinitiated by the server, somebody in the cloud switching ressources, some random timeouts, ... etc... ?