My Published Bot Refuses Give me the same result as the Studio version

Is anyone able to answer the question:
“What would cause the Bot to perform differently in its published version compared to its unchanged Studio version?”

Both the bot in Studio, and its published version within UiPath Assistant, have the exact same version number etc. No changes made after publishing.

I run the Studio Bot, and my files are exactly as I need them.

I run the exact same bot from UiPath Assistant, and it changes the time and date to an older version of the files (even when I use renamed, new, copies of these files).
And the files that I end up with have the exact same data they started with, as if the bot hadn’t run at all - or as if I disabled saving the excel files - which would have crashed the Bot somewhere along the process. Which means that it isn’t the case somehow.

Please help me, I am repeating this experiment and expecting different results, but keep getting the same result - which is the definition of madness.

This is what it should be (what the Studio Bot produces)
What it SHOULD be

This is what it ends up as (what the UiPath Assistant version of it produces)
What it ENDS up as

Oh no. I’m seeing this behaviour with other similar Bots as well. The UiPath Assistant Bot isn’t touching the files it was meant to… I wander where the files its manipulating are… because it sn’t failing, & I clearly see the spreadsheets it’s editing while the process is running… :neutral_face: :slightly_frowning_face:

You know what! I’ll see what happens when I run the Bot after deleting the files - because it doesn’t seem to be changing them anyway.

Ah - I see now - it recreates them - I can’t believe it has taken me a year of using UiPath to notice this… Why is it only doing this now tho?

It was perfectly fine last month - all the tests gave me the results I was looking for.

new issue - Now that the previous one was resolved - I have a new problem where the UiPath Studio Bot runs just fine, while its Published UiPath Assistant version (no alterations were made after publishing), just ends up crashing within 40-50 seconds. It’s an error that sais “The source data has no rows or columns.” - but since I can’t replicate the crash in Studio - I can’t figure out the root of the problem.

Edit:
You know what - I’ll identify it by adding an extra spreadsheet for it to paste data into so that I know what the variables contain at each crucial stage of the Bot’s process.
As well as add Log messages for key locations. That’ll help me triangulate onto the root cause.

Btw, I see you are kinda using this as you’re own ‘thinking out loud space’, which is fine, but the rest of us cannot contribute anything unless you share some code or something.

I can say for sure the issue is in your code. Robots behave consistently, either you set a runtime setting different, although I’d be surprised if this would cause it, or there is some logic in your robot doing it, but without detail I cannot help you identify where.

Think of it like this - someone else might have the same issue - and if they do - they can find the solution - because now it is available.

I would not have added this here without looking at both UiPath Forum searches - and UiPath Documentation searches beforehand. I only post here when the answer seems to be nowhere in sight.

The result of me finding the answers I need - allows me to make my Bot functional (because it was very concerning not being capable of accessing the correct files). Which also allows me to keep my job. Failure is not an option most of the time - & timeliness is crucial, especially if the deadline is overdue.

(I messed up posting with the above 2 replies - apologies)

Yeah, and its fine to solve your own problems and share that on here so others can benefit.
But I am not sure this topic can provide that benefit since its not clear, at least to me, what you are doing so it wouldnt personally help me.

You mention reading files, but its the wrong ones, but we don’t see how you read them so have no context for understanding the problem, nor the ‘fix’. Its considered solved by you because it recreates the files it tries to read apparently, I assume you are on modern Excel and the property the create a file if it doesn’t exist is on, but as you see I am needing to make alot of guesses.

I encourage you to use the forum, and to share solutions, but consider the detail, it needs to be both detailed enough for us to understand whats going on, but concise enough so we aren’t lost in details.

1 Like

To Summarise and Conclude:

I did not realise, that if you use a file-path that is only the file name or folder name (hence held in the same folder that the project is in) - that it will recreate those files for the published version of the bot - so running the published version will not update the files held within the original UiPath Studio Project folder.

This is due to tests I ran - which always gave me the results I wanted - blinding me from realising the truth behind how UiPath Assistant actually works.

Hence why you need to pick a folder and/or file held outside the project folder - so that it will also use the exact same file/folder once published.

By the way - for those who want to know - you can access the Published version of the files (such as Excel or Word) by pausing the Bot while it has opened a file that it is working with - and than click File, select “Info” - & select “open file location”.

It will. lead to a file path similar to
C:\Users\username\.nuget\packages\Project.Name\1.0.0\content

I also have a separate issue where the UiPath Studio Project runs smoothly - but then when I publish it to UiPath Assistant - it crashes. This dual behaviour makes no sense - from my perspective - that should be impossible. I can’t afford to waste time solving a problem that shouldn’t even exist in the first place. (I will post the cause and solution of the issue asap, either here, or linked to this message).

The most relevant UiPath Documentation I could find on the topic was this

And it still doesn’t quite provide the information detailed in the summary above.

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