I am facing an issue that by Scheduled jobs doesn’t run when my Remote Desktop connection is disconnected or locked(Win+L). Note: Its working fine when minimized or logged in state.
I tried to search this issue on ongoing threads but no solution worked yet. I read that there’s something that disables UI object when you disconnect RDP. But no any specific solution to allow UI robot to start his own UI session.
Can you please provide a solution so that robot can work even if I disconnect my RDP (Remote Desktop Protocol) session?
interesting! so you are able to see the bot take over and start the job and still have the ability to watch the desktop as its running? Probobly a Remote Desktop/ Citrix thing. I’d like to see what happens to the robot status in Orchestrator when you close out of Citrix.
Then job fails and gives error that Desktop has been disconnected. Doesn’t the robot creates a session for itself when I disconnect My session? or is it that it requires an active session and use it run a job.
@Forum_Staff Can you please let me know if this is an Identified issue and you have any plans in next release or something? I have tried all the solutions, even read the Interactive Session posts and all I conclude is My Robot is unable to create its own session and run a job when RDP is disconnected.
A tons of Topics on this error with Majority with No solutions!
@Ravi_Chotaliya Could you check to see if you get the same error if you trigger the robot from the orchestrator while you are not connected to it with citrix. It sounds like you are triggering the bot from orchestrator, watching it run in citrix, disconnecting from citrix, then getting the error. With a regular remote desktop connection you would typically get kicked out if the bot started up.
I’m hoping that you have better results with this if you try to run the bot without being connected first, then watching the status in orchestrator to see if it errors out. Hoping this works!
Please observe that in case of Community Edition the Robot service is working under User Thread:
So if you have logged off or session is locked this service will be not responsive. It’s the main reason and limitation of CE version. You can install Robot from EE msi package so your service will be “System” based.
Should work but there will be other problem. Community Edition is updating automatically. Robot installed from MSI will stay in the same version constantly so you need to update working path to robot on every update.
I think so.
Please remember that it’s only a hint. It’s not by any way official UiPath solution. Normally the solution for this is to just buy Enterprise Edition and work with it.
I wouldn’t call it an issue. With Studio Community Edition you have by default Robot and one attended robot type. Only Community Orchestrator offers more robot licence types but those (like unattended one) will not work fully with Studio EE because of limitation.