Unattended bot issues- won’t invoke workflow

Help Orchestrator
, ,
1

My unattended automation seems to not be working.

The automation works attended on multiple machines but after I published it to orchestrator and ran it things it stopped working. It hits a log message saying it’s invoking a workflow but then gets stuck and never invokes the workflow or something. The workflow that it is supposed to be invoking starts with a log message and that never gets hit. There is no error or anything just stays in “running” status.

Any suggestions would be very helpful.

2

Hi @Karson_Dunford, Welcome to the forums!

May we know a bit more details about that specific workflow?

  • For example, some SAP instances might block UiPath, not allowing the timeout to even start, and staying there forever unless working it around.

Another option I can imagine is the way that the unattended robot is installed in the PRD machine. Ideally for unattended, it should be Service Mode, but you then need to make sure that if anyone entered that said machine with the robot user, they have signed out properly, as otherwise the bot logs in, but “inherits” the old session left by the user, and can act as if it was attended (and some UI Interactions might fail)

3

The bot successfully logs Into a service performs a search then verifies that the search resulted in records being found after which a work flow that uses table extractions to pull data off the screen on top of some data table manipulation is invoked. Everything completes as I would expect and the logs are all correct up until the extract and processing workflow is invoked at this point it just gets stuck running and I’m forced to terminate it. the last log message that shows is just before the invoke activity.

Before publishing the automation I did log into the machine the bot is on and attempt to run the automation as an attended just so I could see it run but it gave some message about being unable to because I was trying to run it in attended, I can’t quite remember what it all said but could this maybe have caused my issue?

4

I get you, then, am I right then with the following assumptions?

1- This process never fully executed on the current machine (You tried manually, but you got the message mentioned)

  • When you tried to run attended, was it from Studio? Or from Assistant after publishing?
  • No need for the exact message, but was it something about PRD License being used, therefore you can’t debug/run from studio?
  • If so, you might need to trigger Maintenance mode from the Orchestrator, to allow a PRD license to run in attended/debug for a limited time to test it in the PRD Environment.

2- It is Web Automation (Login into Service Platform, Navigate, Extract) + Data Manipulation (Workflow that fails)

  • The last message shown is before the workflow is invoked, do you have log messages inside the said workflow?
    *What does that workflow use as arguments? I guess the DT to be manipulated, but any other input?
  • Would it be possible to get a demo XAML zipped here (removing any sensitive data) to double-check if it might be anything related to properties? Ideally from the failing workflow and a sequence simulating the invoking method you are using for the said workflow.

BR,
Ignasi

5

I did try to run it from studio on the machine while testing it. And that’s when it gave the weird message. It wasn’t like a log message, it was a popup from studio.

The first activity within the attempted invoked workflow is a log message and that log message never gets ran. No system exception or anything is thrown. It won’t timeout either it will stay running until I manually terminate it.

6

Also there are no arguments that are passed into the invoked workflow.

7

Well I logged on today to start debugging more and I’m getting an error I didn’t get in 50+ runs yesterday.

“Expression Activity type ‘VisualBasicValue’1’ requires compilation in order to run. Please ensure that the workflow has been compiled”

8

It now ran successfully from orchestrator.

I think for some reason orchestrator was catching that error but not I had never seen it in studio so I had no logging for that error. So I corrected the error, it was just a bad quotation and then republished the automation and it works as expected.

1 Like