Issue with unattended mode

Help Orchestrator
1

Hello team,
During the PROD Go-Live - we find that the BOT fails when scheduled in unattended mode. On further investigation it was found that issue might be because the screen resolution is getting to a smaller resolution due to which the BOT could not find the designated place to click or take the required action, in some of the screens. Hence, it failed.

Have you any idea on this?
If we change robot resolution in orchestrator as 1920* 1080* 32. Is it impact old process?

Can any one please help this?

1 Like
2

@raviteja.ponnavada

Welcome to the community

it depends on what resolution the old processes need…try to change the robot settings thats the only way to resolve resolution

part from that you can use a simulate or chromium api instead of hardware events ..which will work even if not visible on screen

Generally settings a higher resolution might not effect other bots as they are already working proper in lower resolutions..

cheers

3

I would suggest to change the Machines Resolution that is suited for your process when you did testing in lower environment and then try

4

Hi @raviteja.ponnavada

Please change Robot Resolution to 1920Ă—1080Ă—32 and try to use best practices.

Cheers

5

Welcome :slight_smile: to the community.

It mainly depends on what screen resolution the existing processes require.
Try changing the Robot resolution settings, that’s the only way to truly fix resolution-related issues.

Alternatively, you should use Simulate / Chromium API instead of hardware events, as these will work even if the screen is not visible.

Usually, setting a higher resolution will not impact other bots, since they are running fine at lower resolutions…

6

@MohammedShabbir

Atleast while copy pasting make sure you dont copy the original message

cheers

1 Like