The robot on UiPath Assistant, which has been used continuously about twice a week since January this year,
After the UiPath version update (V2022.4), it suddenly stopped with the following error (The workbook does not exist). Do you have any idea about the cause and countermeasures?
Regarding the message that the workbook does not exist, we have confirmed that there is no corruption or data abnormality in the input/output files used by the robot.
Other points we have confirmed are as follows:
The original files of the robot can be debugged and executed successfully in UiPath Studio.
No improvement is seen even after republishing the robot file.
Based on the above difference in Studio/Assistant behavior, the nupkg file expansion destination (C:\Users \ [UserName].nuget \ packages \ [Robot Name]), but no file corruption or over data was found.
The above phenomenon was also confirmed on another PC (the above phenomenon was reproduced on two PCs in total).
It is user data and confidential, So screenshots cannot be attached.
Details in robot using excel data are as follows
Invoice format data
Extension is .xlsx
We cannot detect which activity failed because the debug run in Studio succeeded.
We think the error is occurred by the bug due to UiPath’s update because
・The error suddenly appears after UiPath’s update to Ver.2022.04
→Before update, it had run properly without any problems.
・We made sure that required files to run the robot are stored in correct folder.
We haven’t changed anything, but the error has occurred after the update. I can’t guess any causes other than the bug.
On the other hand, we would like to escalate to UiPath Support, however, Ver.2022.04 has not been provided in Enterprise Edition and UiPath said “We cannot answer to question about Ver.2022.04”. Therefore, we posted it to Forum.
(We have posted same question to Japanese Forum and found the user has same situation but no one has idea to solve this.)
Anyway, we are still researching for this issue.
Thank you for your support.
You can say that again.
I’m super surprised about UiPath since “Debug” and “Run” use Assistant App either, but the issue only happens when I use published package via Assistant App. I think no one have an idea…orz
Anyway, if you find new info, please provide and help us.
Super strange. Any chance you are able to reproduce this behaviour on a fresh, new project with some dummy data? Or is it something that only concerns old projects?
Lastly, just so i got it right - this error only happens on runtime? If so, could you try outputting some logs before and after some potential activities to try to identify the faulty activity?
Maybe one more thought. Are the paths to the excel file dynamically generated, or hard coded? (Having a screenshot or a few of the activities configuration might also help a bit)
Thank you for your reply
I am sorry for the delay in answering due to public holidays in Japan.
What do you mean by new/old project?
There is no change in the robot program data, only in the automatically updated UiPath Assistant (v22.4). The problem is not only with the original robot file (UiPath Studio v21.10), but also with the re-published robot file (UiPath Studio v22.4).
The error occurs only when running UiPath Assistant (not debugging or running in Studio).
We have been able to identify where the error occurs.
(We have created and published a robot with messages inserted at various locations)
The following Config file is loaded.
This error occurs during the first operation of the Excel file.
Thanks for the reply.
An additional question provided a hint to identify the cause of the error.
The UiPath Assistant seems to have the following bug:
Default value of Argument in UiPath Studio losts on publish for UiPath Assistant.
When I created a robot that displays Arugument as it is in the message box, the default value of Arugument is displayed when running in UiPath Studio, whereas nothing is displayed when running in UiPath Assistant.
A temporary solution is to use variables instead of Arugument, but I hope this bug will be resolved soon!
Hi @nosawa thanks for sharing your bug report! I am experiencing the exact same issue with the default argument in the workflow somehow being “lost” when the process is run in UiPath Assistant.
Hope that UiPath fixes this issue ASAP because this is a big problem. I am going to be going back to the old version of Studio for the time being.