Read Text File: One or more errors occurred. Could not find a part of the path

Hi friends!

I found an error while reading my text file in the community version. After searching the forum, I couldn’t find a solution, so I decided to inspect my workflow using a code editor. I found the following:

On line 115 of my workflow, it adds a data [U+202A] which refers to a specific Unicode character known as “LEFT-TO-RIGHT EMBEDDING.” This character is used to temporarily change the text direction in a bidirectional context, such as when Hebrew or Arabic text is found within an English document. I’m not sure where this came from; whether it’s a bug or a confusion in the community version, but it needs to be removed to eliminate the error.

Greetings, I hope this helps some who are experiencing the same issue.

Hi @MickQ

Share the error that you got in Read text file activity. After bot execution fails open the output panel and share the error here.

What does it look like in the activity in Studio? You probably accidentally copied/pasted that path with that extra character.

Hello @MickQ

The extra character can be sometime due to the extra space in the url, try removing/replacing spaces from the url/ folder names and retry.

Hi friends!

Sorry for not sending an image earlier. I’m uploading it now.

You can see that I’m sending my input to the ReadTextFile activity using in_Config(“MailOK”).ToString. Similarly, I’m using it in intermediate to show that I’m sending the correct variable, and it returns the value:
“‪C:\Users\Administrator\Documents\SCL_consultores\RPA_Conexion_Zscaler\Data\Input\Plantillas Correos\Email_notificacion_correcta.html’”
which is the file I want to read.
The activity is reading a different path.
“C:\Users\Administrator\Documents\SCL_consultores\RPA_Conexion_Zscaler\‪C:\Users\Administrator\Documents\SCL_consultores\RPA_Conexion_Zscaler\Data\Input\Plantillas Correos\Email_notificacion_correcta.html”
As I mentioned earlier, my solution was to send the path directly without using variables to parameterize it in the Config.xlsx.

Hi guys!

I found the real problem after reviewing it with all possible options, and it turned out that this bug occurred in UiPath Studio version 23.12. I solved it by creating a new project and migrating my workflow to version 24.2.

I didn’t imagine that the 23.12 project version had that bug.

Thank you all for your interest in helping me.

Regards.

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