@gis_mags
I've had 3.5 crash a few times after getting back to a computer and unlocking it. Also seen behaviour that looks as if it takes a while for it to connect back to online services after an unlock - not long, just may need to refresh a map twice or it redraws a web service with tiles missing; then after a few seconds it's back to rendering as usual.
What you describe may be the result of the data itself not having a coordinate system assigned, and Pro losing the basemap on wakeup/unlock. It may then revert to Unknown as that is what the only other dataset in the map has.
In a more complex organisation there may be limitations on internet access while a pc is locked and a user's access is only granted again at login/unlock. A few seconds delay can get some waking processes out of sync and some apps don't handle it as gracefully as others.
I would double check that the data is set up properly and if the behaviour is the same with only local, located, data.
Your colleagues may have to be willing to go on multiple lunchbreaks per day until the problem is solved..... Issues like these can take years to resolve 🤣
