Hello!
Don’t get me wrong : the process works perfectly in Studio and is also considered as a ‘success’ when I execute it with UiPath Assistant.
The problem is that it looks like it doesn’t show the actions I’m expecting.
For instance, the UI automation activity like Message Box are not displayed as well.
I feel a bit lost in this area so thank you in advance for your help.
LdR
Hello @LamaX,
Republish the process and then update it in the orchestrator folder and then try to run it from assistant.
Regards,
Bharat
Hey @LamaX could you show us the Logs from the orchestrator and also show the assistant screenshot.so that way we could help you more better.
cheers
@bharat.c
There’s no change with this.
@singh_sumit
In the logs section (in orchestrator), I’ve just found the beginning and the end of the process.
I didn’t use ‘write line’ and ‘log message’ activities.
Kindly enable Simulate or Send Window Messages in the Properties panel of the activity (like Type Into) and the re-publish and try. If the issue still persists. Then, go to Orchestrator, remove the existing machine, and add it again to generate a new Client ID and Client Secret. Copy these credentials and paste them into the Assistant.
Oh you seems right!
I didn’t do it yet because they are like “Are you sure you want do it ?”.
Here are the problems i’m facing I guess :
So I just have to delete both machines and recreate a new one.
The new IDs have to be added to UiPath Assistant.
Is that right ?
Hey @LamaX could you add Log message and pass the same Message box value into the Log message .and then publish the new package and then try run new publish package.and before doing that can you check project.json and inside that try to find entrypoint and if “isBackground”: true make it false .
or If the robot is running under a background session (for example, started from Orchestrator or through a scheduled task), UI activities like Message Box won’t display because the process is executed in Session 0 or Non-Interactive mode.
cheers
Yes,
You can delete the machines and add the same machine back you will get Client ID and Client Secret. Copy these credentials and paste them into the Assistant.
ok @LamaX can you do one thing like in the new update many of the fellow member are facing that type of problem.as per the solution is go to orchestrator remove the machine and add that same machine again that it will generate client ID and client Secret copy that and paste it to the assistant where are you running your unattended bot. now your are good to go to run your process again. and before doing that if this happen in type into or any ui activity kindly enable the simulate/send window from the property panel of that activity.
