Hi,
I believe I've encountered an issue with PAD error reporting.
Let me explain the situation.
I have an .xlsx file that is a kind of database of clients and their data.
For each row (client), robot needs to download certain reports and organize them in file folders.
Before it downloads the reports for a certain client, it extracts client name via SQL select, and creates a folder with the same (client) name.
Downloaded files are located in the system download folder first. Robot renames them first to a non-generic filename and then moves them to the previously created folder. So the actions are "Rename" and "Move".
The issue arises after the successful renaming. In the "Move" action, as the source I state %RenamedFiles[0]% and as the destination %ClientFolder%.
The error I got when it tried to execute the "Move" action was "Source folder doesn't exist" which would mean that the system download folder didn't exist.
I checked all the variables at that point multiple times. Literally pasted the %RenamedFiles[0].FullName% value into file explorer and it opened the correct .pdf file. So the conclusion was that was actually nothing wrong with the source.
After a bunch of checking I found out that the issue was actually in the destination folder. As it pulled the client name from the .xlsx, some clients were named with a space at the end (client name ), but since that value was passed in the variable during the creation of the client folder and given the fact that the system doesn't allow creation of folders named with a space at the end, the issue was in fact in the destination, not the source.
I would recommend this issue to be fixed and correctly reported in the future, it would save some people a lot of time.
If any additional info needs to be provided, I'm always reachable here.
Cheers
p.s. I know that the downloads folder has some known accessibility issues, but this was definitely not the case here because all of the correctly named clients (without space) were processed without any problems.
