Remote debugging works fine and I love it apart from one thing. The timeout. Unless I stop all other processes running then it will timeout waiting for available robots. There is no way to set the priority of the job or alter the timeout. Any ideas anyone?
Hi!
Are any of the robots available when you remote debug?
Do you leave the settings like this or do you specify a certain user/machine?
Hi Sven, yes as I say I can absolutely connect . I just have to make the bots are not already busy by turning off triggers in orchestrator. If the bots are already busy then the connection will timeout. If the bots are not busy I am able to connect.
I specify the machine and user as there aren’t multiple available in this case. We are using modern folders, so it’s more the license count that is the issue. There is not a free license and it can’t wait lon enough for it.
Ok!
It makes sense though, that if there are no available robots then you’re unable to run the remote debugging 
The remote debugging job will queue for a short time, and as you mentioned there doesn’t seem to be a way for us to increase that time-out.
Do you have any NonProduction or Testing robots that you can use instead of your regular Unattended robots?
The issue is on a testing license in our test environment, we just have a very limited number of test licenses (to save cost). If I ran the job from orchestrator the pending job would remain there (indefinitely) till a robot is available, giving orchestrator the chance to queue the job up. Either that or I would set priority to critical on the job to make sure it runs next. With remote debugging I have about 30 seconds, so unless there is a plethora of unused licenses I am not getting on!