Hello,

You can validate this:

-Make sure the BOT screen resolution in attended mode is the same that the resolution specified in the schedule (if is the case) for Unattended mode, sometimes different resolution can cause the controls to move different position and can change some object criterias causing this type of error.

-I don't know if you refer Attended Mode as the development environment and Unattended Mode as the production environment, but make sure that both environments are equal. Same browser, preferably same version, same resolution, no zoom.

-Sometimes when we navigate a web page if the BOT are executing the steps too fast don't allow page to load completely and can cause that sometime don't find some controls, try to add a Delay before clicking the element, analyze behavior.

-In case that you have a dynamic generated controls on a web application (I see this behavior on SAP Ariba web app), you need to find another ways to search for the control, possibly the use of regular expressions.

Thanks,

Christian Torres

Hi,

Sometimes a hidden modal or floating banner in unattended mode can block the object invisibly. These may not be captured in screenshots or appear in a different position.

Try running the bot using “Attended Mode” for testing within Control Room, this can help simulate the unattended session behavior more closely and expose hidden timing/UI issues.

Hi ​@Sakshi ,

What is the screen resolution defined for your Runner machine? 1366x768 is what the recommended one.