Selector fails when RPA process run from Orchestrator, but runs correctly from attended bot agent

Pervasive issue with running RPA process from Orchestrator. Attempting to enter a filename in a Windows Office Save As input popup. Runs fine attended, fails from Orchestrator. Had to pare selector to bare minimum of lines. Spent over a day trying to figure out. Orch bug?

Selector -

From this:(fails from Orchestrator)

To this:(works fine from Orchstrator)

if the latter one also works in attended, then you should use it instead… im sure it is not a bug, when you are developing something intended to use in a background environment, you need to make sure to use the right selectors and options (and no activities that need foreground).

It is a foreground activity. I can recreate. It is a simple save as popup with activity of type into file name input.

I faced similar issue, when I click upload button, I get another window.
I changed the Simulate click activity to false, it was all ok when I ran from orchestrator

We‘ve seen strange behavior sometimes with Office applications in service mode robot. We tend to either use workbook/exchange activities, where possible or try to let the robot run in user-mode.

Give it a try…

i think i have a a similar issue as this, if i try to run a job through the live orchestrator it keeps failing without giving any error or log but once i log on to the server where it is hosted and try to run from the uipath tray then it runs without issue. please help
see sample below;

Hi @olumide.akinnayajo ,

DO you found the root cause and the solution of the problems? Cause I also facing the same issue.