Hi Team,
I am facing a weird issue in UiPath, I have created a simple Agent and Call the simple RPA workflow where I have put message box and logs, it seems it is executing but the RPA Workflow is not executing the message and prinitng logs, i don’t understand what is the issue is, it is simply wasting time.
@ashokkarale please help
Hi @balkishan
I might be wrong but i think this could be about where the robot actually runs. When the agent calls PrintResult, that workflow doesnt run inside your Studio Web session, it goes out as a job in Orchestrator and runs on whatever robot is set up in that folder. So is the robot configured on your own machine, or is it pointing to another machine or a serverless one? if its not your machine, the Message Box would be popping up somewhere you cant see, and if its unattended it might just be sitting there waiting for someone to click OK, wich could explain the time it takes too
other thing worth checking, where are you looking for the logs? if you’re expecting them in Studio Web they wont show up there. Try going into Orchestrator, your folder, Automations then Jobs, find that PrintResult run and open it, the Log Message lines should be in there
if you can share what the job status looks like there (successful, running, faulted) that would help narrow it down a lot. and maybe try swapping the Message Box for just a Log Message for testing, that way you dont depend on a screen at all
Thanks for your reply,
Actually i want to call the RPA workflow where i have given a message box & logs to print the result which will come from Agent, but the message is not coming even the logs is not printed, where actually i can see the logs and message, it is running on a cloud, i tried to run only the rpa workflow and switch the debug to run on local machine and it is working fine,
but when I debug the agent and agent call the rpa workflow that time i don;t see any logs, message and it is showing successful also after executing.
where i can see the logs of the rpa workflow , i have a question then in real time scenario it is very difficult to debug, develop if we can’t see the things on local machine, i noticed one thing , this agent we can;t run on local machine it can only run on cloud.
kindly guide
I did not publish this agent, will it still show the logs in the Orchestrator → Automation ?
Check the traces and see if the RPA workflow was invoked /called by agent or not.
If it was called, then check the jobs in the orchestrator folder and see if it was ran successfully or not.
Hi , it is called, and showing successful also, but my question why it is not writing the logs in the output to see if it is running or not , even there is no message also coming if it has executed, if this is case, everything is running on cloud, in real time scenario , let’s say there is scenario, my agent will call rpa bot and the rpa will open the portal and perform the task then in this case how will debug, check and monitor, it be a challenge then. if this small message box is not appearing on the screen, kindly suggest and guide please
Hi , it is called, and showing successful also, but my question why it is not writing the logs in the output to see if it is running or not , even there is no message also coming if it has executed, if this is case, everything is running on cloud, in real time scenario , let’s say there is scenario, my agent will call rpa bot and the rpa will open the portal and perform the task then in this case how will debug, check and monitor, it be a challenge then. if this small message box is not appearing on the screen, kindly suggest and guide please
@ashokkarale @Michael.Vornes
[/quote]
Thanks a lot, can you please reply my query, in real scenario how we have to tackle this.
Logs will be visible in the logs panel on the orchestrator and in the traces as well.
This RPA workflow will be ran on an unattended robot. So if you have configured a serverless machine, you will have to see the bot run through live streaming of the job. You can assign your local machine as unattended and set to run the jobs in that perticular folder. So all the jobs running will run on your local machine so you will be able to see the execution.
