Process fails to run when machine is not moitored

Help Robot
, , ,
1

Hello everyone,
I have an issue with a process I recently created. I have multiple VDIs which I use for my bots, but recently the newest VDI doesn’t seem to work properly. Whenever I run the process from the Orchestrator and I am not monitoring the job the bot falis to complete the first step which is the login screen (it somehow gets grayed out/brought to the background, and the bot doesn’t click it at all) and I tried fixing this by adding ‘Activate’ and ‘Set Focus’ activities but its still the same. The very same process works fine when I am monitoring the process (I have opened the VDI and I am watching the bot work) and also on other VDIs without monitoring.
What might be the issue, since this is a new VDI maybe I haven’t set it up properly? What should I look for to make sure the processes work in the background?

2

Hello @Dea_Pahumi

from what i read i think it may have many factor that affect your process to not working when not monitoring
Let’s have a checklist below

  1. Login screen timeout: Ensure that the login screen doesn’t have a timeout that causes it to be grayed out or minimized when there’s no user interaction for a certain period. If there’s a timeout setting, consider increasing it or disabling it.
  2. Background execution: if want to use it to work as background then we should use simulate click or type
  3. Screen resolution: Verify that the screen resolution and scaling settings on the new VDI are the same as on the other VDIs. Mismatched screen resolutions can cause selectors or image-based automation to fail. You can configure the resolution settings in the Orchestrator for your robot to ensure it uses the correct settings.
  4. VDI settings: Check the VDI settings, such as power options and sleep settings, to ensure that the VDI remains active and doesn’t go into sleep or hibernation mode when not being monitored. (I think this one is might be the closest solution for this)
  5. VDI performance: assume that both VDI have same spec
  6. VDI access rights: Ensure that the robot has the necessary access rights and permissions on the new VDI to interact with the applications and perform the required actions.

Hope this checklist can help you get some solution for this but if not let’s find out other solution together

Best Regard,

1 Like
3

thank you for your reply @NutchanonSwnl I think it might have to do something with the access rights. I will further investigate and if the issue still occurs I will reach you out.

1 Like
4

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.