General Function Failures - Why?

[MillionMap]

I can open and use Pro without a problem for a while but inevitably I get "General Function Failures".   I close the app and open again, everything is connected correctly, but at random times the errors display once again.  I'm doing nothing different than I've always done.  I'm using the same type of data I've used for years.  I'm running 3.5.1.  Another user opened my project and she is also getting these failures, and she is running 3.4.2.  She has never had this type of error before until she opened an aprx I created.  The very confusing part is nothing seems to be wrong for several minutes until suddenly my connections are lost. 

[MichaelVolz]

Do you have web service layers that depend on a good internet connection that is somehow being dropped?

[MillionMap]

Yes, I’m using several web service layers but the failures seem to be on internal server based files.  I haven’t tried, but if everything was on my local machine it may solve the issue. But I don’t want everything local.  

[mrmark]

Came here looking for some help. I'm on 3.5.2, but otherwise same story, except I have NO web layers. All layers are coming from Geodatabases that are on network shares or the local machine. 

It is the layers in the local project geodatabase that suddenly stop drawing. Any solutions are appreciated. 

**Also - layers that stop drawing seem like a pretty big deal. Took me quite a while to see the TINY red exclamation mark at the bottom of the screen. And notifications that say "General Function Failure" don't need an option to see MORE only to find that the more also says "General Function Failure" with no additional explanation, link to help, or anything useful. 

[PiesSky]

 I too am experiencing this issue, as per OP

[MillionMap]

Locally stored files, this error does not occur.  Server based files, which is how we've stored files for years and years is 'for sure' the issue, no clue why this started all of a sudden.  I wish I could answer exactly why this happening far less than before.  After an ESRI ticket and multiple conversations, my company's IT department has done things to our server that has minimized this error to a rare occasion, rather than a multiple times a day occasion.  I did uninstall and updated to 3.6 but I wouldn't consider it the fix.