CLONE R4 - SignalR Failure catch

When something goes wrong in the SignalR communication process, it appears that SignalR does an auto-retry. The problem is that if the communication cannot be re-established it will loop indefinitely which may be making tons of unnecessary calls which in certain places (like the menu) has caused the database to get overloaded.

What we need is some sort of control over this process to prevent database overload and possibly alert the user there is a possible issue.