Automation functions differently when published and used through the assistant instead of through the studio

Help Assistant
, ,
1

I made an automation that collects unread emails from 2 outlook mailboxes and scrapes them to place orders into our production system using an API call. There is a third mailbox that is also checked and it will send a reply email as a form of accounting for errors.

When I run this from the Studio, everything works as designed. I don’t have any design issues, that I know of. When I publish this and run it from Assistant, I’m encountering bugs. The bugs seems to be occuring when I make an update that is unrelated and publish it to the orchestrator.

This includes:

  1. It is skipping the sequence where it checks the inbox for errors, or it is incorrectly not finding an email that is present.
  2. There is a specific update I made (quite a few updates previous to the current version), that has now revrted back to the original state before that update and I have no idea what is going on. It works as designed in the Studio, and it’s not working the same when I publish it.

Sorry if this has been covered already somewhere, I wasn’t able to find something that seemed to be what I was looking for.
My Experience: I am definitely a novice. I am studying for a B.S. in Cybersecurity and I took an RPA class as an elective and have applied it to my job to solve a problem. I was able to get to this point without posting but now I’m stuck. Any help is much appreciated.

2

can you tell exactly on which activity or which place you facing error ?

its helpful if you share error message

3

Hey,

Can you use logs to track where its exactly failing.
Also regarding update. can you check with your admin he can show you audit logs who reverted or how did that change.

Thanks.

4

There aren’t any error messages that pop up. It runs perfectly from the studio. When I run it from the Assistant, it runs successfully but it doesn’t function the same as when it is run in the Studio. Some of it works, some is ignored, and some is behaving like it was before some updates were made a while ago.
This sequence is being ignored when ran from the assistant.

image
image629×543 17.1 KB

5

This part is an update I made a while ago that isn’t working on the assistant.
Again, this functions fine when run from the Studio. Bascially the user is entering the states’ abbreviation and I am using a data table to create a relationship for the long form value and then placing that into the json for the API call.

image
image637×661 21.4 KB

I believe there is another section that is also behaving as if it did before a previous update but I’m not 100% sure.

6

Where do I look for the logs to see? I can look into that myself as well. I am the admin, developer and everything. I made the change a long time ago and it has been in effect when I run it through the studio but I think it’s been malfunctioining since I published it and started running it from the Assistant.

7

Or it could have changed when I published an update to the Orchestrator, I’m not sure.

8

After publishing the package from Studio, are you going into Orchestrator and updating the Process so it uses the latest package? This isn’t automatic.

9

Okay I’m looking into this. The thing is that the new updates I make will validate testing when I upload it to the assistant but then old ones will break.

10

I resolved this! Thank you everyone for your input!

I managed my package wrong and the orchestrator was using the wrong .xaml file and I didnt know. I went to My Workspace → Automations → Processes. Right clicked my process and noticed that it was using a different xaml than I was expecting.

I was trying to use the OrderEntryBotMain.xaml not the BuilderOrderEntry.xaml

I updated this xaml to have the correct workflow and all is working!

image

11

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.