Available robots on Orchestrator cannot start executor on VM

Help Orchestrator
1

Robot connected with VM looks available on Orchestrator, but cannot start executor on VM(or RDP session), so job went faulted with error message below. (Job was working well before, I guess this error occurred after something happened in VM.)

Could not start executor. Rdp connection failed: Message: The connection transport layer failed., Last error: 131085
image

Issue occurs due to “remote session” server issue, even cannot manual login VM.
image

Questions:

  1. Since the “remote session issue” exists, why does Orchestrator still show everything normal, and robots are available and connected to VM?

  2. How to monitor and notify this rdp session issue before running any Orchestrator jobs on VM? Do we have to notify this issue only after running jobs and see they are “faulted”?