I have an automation that was originally built as attended, but recently updated to be unattended. The attended version works fine, but unattended it doesn’t seem to be executing the steps properly.
The automation goes onto a website and clicks on a number to update it. The new number from the website is then recorded on an excel sheet. I have log messages and can see it going through the steps, but it doesn’t seem to be either clicking the number and/or reading it correctly (the number always comes back as 0. when checking manually, it isn’t 0). Both the clicking of the number and the reading of the number are done with the inject Js script activity for the attended and unattended versions. I still have the attended automation active and everything is still working in the attended version.
Do you know if the unattended robot is set up correctly?
Reading between the lines, would I be right in guessing this is a new setup in general for unattended?
A way to test is if you just make a simple workflow that takes a screenshot, try to start that bot unattended. If it works then its 99% sure your unattended is set up correctly and not the main issue.
My theory is that the session isnt properly logging in and rendering the screen, which interferes with your code. The above test should help determine if my idea could be right?
I believe it is setup correctly. It is my first time setting up an unattended robot. I did the screenshot workflow right now like you suggested and that worked. I can see the screenshot is of the desktop where the unattended bot runs.
Ok nice. Unattended setup is a thing that often trips people up their first time.
What happens if you run the automation via studio on the unattended desktop session? Does the code run?
And when you said you were running it attended in the past, do you mean via assistant? If so repeat that on the Unattended machine to see if you get any difference. You basically need to isolate the difference, is the way the automation is ran or the machine / session its ran on.
I did the testing as you recommended and was able to identify the issue. It ended up being an issue with the website and not the automation. Thank you!