Well, to just say it is a “network issue” is making an assumption. I too have encountered this same exact issue. We engaged both Microsoft and UiPath to perform logging and tracing in order to try and identify the root cause of this issue.
As for Networking, neither Microsoft nor our Network Admin found any issues with out Network. All Traffic was making it to Orchestrator.
Orchestrator seems to be at the heart of the issue, but UiPath was never able to point to anything definitive nor provide any fix, only the “workaround” as described above.
We were on version 18.4.3 and never had this issue. It was not until we migrated to version 19.10.4 that we started to see the issue occur. We just not upgraded to version 2020.10.4 and was hoping that might resolve the issue, but again, it did not.
Not sure if this is all related to Robot-to-Orchestrator communication protocols such as Long Polling or SignalR, but something is going in with Orchestrator, that is for sure.
I can just be sitting, logged into Orchestrator Dashboard with my Browser and all of a sudden, will see messages pop-up in red telling me “unable to connect to server” and then I have to refresh the browser.
Wondering given Orchestrator is running under IIS, if it is some IIS setting…or something internal to Orchestrator…?