Error in Initializing Application

Hi Team,

i am trying to interact with MTPutyy application using Modern activities but BOT is working fine in attended Mode and in Unattended Mode this is not working, like BOT is not able to bring up the application or interact with the application, why so… how can i fix this.

pls see if i need to modify any properties

Hi @devasaiprasad_K

Try using the activate window activity and indicate the data that is present when the application is launched and that helps you to bring the application into the foreground.

Regards

Hi @devasaiprasad_K

Try using the below activity which is present in classic activities and indiacate the data that is present once the application is launched and that will help you to bring the application to foreground.

Regards

Hi,

To isolate cause, can you check screenshot or video when the exception occurs using Recording feature of Orchestrator or TakeScreenshot activity etc?

Regards,

i had the same thought though, is there any logic why BOT is able to initiate the window in attended Mode and not able to bring it up in Unattended Mode?

In the unattended mode the bot will run the browser in background so try the activity mentioned above that helps to bring the browser to foreground and will help you to run that successfully. @devasaiprasad_K

Regards

Hello @devasaiprasad_K

When dealing with the issue where a UiPath BOT works in attended mode but fails in unattended mode, there are a few common causes and solutions:

Environment Differences: Unattended robots often run in different environments (such as locked screen, disconnected RDP sessions, or different user sessions) compared to attended robots.
UI Interactions: Some UI elements might not be available or visible in unattended mode. This is often due to the absence of an active user session or the screen being locked.

How we actually do this and from which version of studio is supporting this, we are using 22 version of Studio and i am not sure if this version is supporting this feature?

pls guide.

Hi,

There is settings for recording in Orchestrator - autoamation -process, as the following.

If you use 22.x robot, screenshot feature can be used.

Or we can use TakeScreenshot activity in Catch section of TryCatch for taking screenshot in exception.

Regards,