Session Disconnection should take into account network error vs empty response #351
Description
Describe the defect
Any network error on the session LAD return currently pops up the ‘session disconnected please reload the application’ message.
This means that if a temporary network hiccup caused that singular query to fail, you have to reload and reconnect to continue to get realtime, even if the websockets were still actually active and working.
I’d prefer if it was a warning if there was a network error or server error, and the current message would play if the LAD response didn’t have the session you were asking for.
Expected behavior
Steps To Reproduce
1.
Additional context