When I’m reading a file to a string(attachment) in a process, it crashes.
If I reduce the lines of the file, it’s going well… It’s not a too large file, but UiPath can’t read it.
Also, for the string type in UiPath has a short String length limitation.
I have a file and translate to base64 encodestring, so the string is too long ,the length is 100044, if I use HTTP Request activities the UiPath crashes like your’s.
I code in Python , it can run and give the right result back.
what can we do with this? I think it is a bug of UiPath, right?
We are also experiencing crashes when too much text is used.
Previously it was known that Write Line and Logging can cause it, however, it’s happening when using the folllowing:
Read Text File, then concatenating to the string when there’s a lot of text
Copying thousands lines of text to the Clipboard.
We have found that this is isolated to certain machines or servers, so as a workaround currently, we don’t run those processes on that machine.
If there is a quick setting change needed, because it seems like some memory-related issue, please let us know what we can try. I have not really dove into this issue yet partly because we don’t know for sure if it’s a UiPath issue, a Server issue, or a combination, and am also unsure which team would best support in a resolution.
I can probably reproduce the crash if I get time next week.
I am using simple “Move File” activity. Here once the destination path is combined with the long file name, the number of characters is cross the 248. Once run them uipath shows below error:
“System exception.The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.”
attaching here the sample xaml.
Can you please share some solution for this.
Add any file at source with longer name (at least 50 characters). FileCopyTest.xaml (10.8 KB)