Robotic Process Automation (RPA)

 View Only
  • 1.  "Wait for download" not working

    Posted Tue September 10, 2024 03:11 AM

    Hi everybody,

    I'm having some issues with a BOT after upgrading RPA Studio to the latest version 23.0.17.

    Long story short, the BOT made a search in a website for documents, then click on the download link for that specific document to download a PDF file. It worked flawlessly until a couple of weeks ago, then I had to upgrade the version and it stopped working with no change to the BOT itself.

    I created another simple BOT to check and the result is the same.

    In this case I loop ten times (just for testing purpose), the first PDF is correctly renamed as "testpdfRPA_1.pdf" and saved into the right path. From the second, it is download in the standard Chrome profile download path and not in the right "\\testpath\PDF" folder. I also tried to reinitialize the variables at the end of each loop.

    Those are my browser settings:

    I tried all the three "User profile preferences" with no luck and tried to change the browser with Edge, same result.

    Any help would be greatly appreciated.

    Thank you very much.



    ------------------------------
    Roberto Innocenti
    ------------------------------


  • 2.  RE: "Wait for download" not working

    IBM Champion
    Posted Wed September 11, 2024 08:50 AM

    Hi Roberto!

    That is very strange indeed. I see that you are using \\testpath network folder as the destination. Out of curiosity, have you tried using a local folder for testing purposes? It should work as it is, but this might help pinpoint the root cause.

    Anyway, I suggest you gather this info and report the issue to IBM support so they can investigate further. You can open a support ticket at https://www.ibm.com/mysupport/



    ------------------------------
    Vinicius Marques
    Data Engineer
    Music.AI
    Rio Grande
    ------------------------------



  • 3.  RE: "Wait for download" not working

    Posted Wed September 11, 2024 09:31 AM

    Hi Vinicius,

    thank you for you answer.

    Yes, I just put a generic fake UNC path in  the screenshot just for example, I tried both with \\path and X:\path (with the samba share mounted as local disk) and I receive the same error (which used to work flawlessly).

    I'm trying saving it locally and then move the file as a workaround, I will let you know.

    Thank you for your suggestion!



    ------------------------------
    Roberto Innocenti
    ------------------------------



  • 4.  RE: "Wait for download" not working

    Posted Wed September 11, 2024 11:02 AM

    Hi,

    I tried and it doesn't work with a local path either.

    The files are downloaded into the "Download path" set in the Start Browser command and neither moved nor renamed into the "Save to" path with "File name" parameter of Wait Download command...



    ------------------------------
    Roberto Innocenti
    ------------------------------



  • 5.  RE: "Wait for download" not working

    IBM Champion
    Posted Wed September 11, 2024 11:17 AM

    Thanks for reporting back. Yeah, that is probably an issue that you will have to report to IBM Support through the link I shared in the previous message. In the meantime, you could do a hacky workaround if your demand is urgent. Something like setting a folder in the Start Browser command that you always make sure it starts empty and then moving the files from there every time you download something. It is not as straightforward as just using the Wait Download command, but that is one possible solution while you wait for a fix after contacting the support team.



    ------------------------------
    Vinicius Marques
    Data Engineer
    Music.AI
    Rio Grande
    ------------------------------



  • 6.  RE: "Wait for download" not working

    Posted 29 days ago

    Hi,

    after some tests I've finally found the issue. It seems that from the 23.0.15.0 version the field "Timeout" on "Wait Download" command must be filled.

    I put something like 30 seconds and now it works perfectly, otherwise the command is totaly bypassed.

    I don't know if this is the real problem and the correct solution, but at least as a workaround it works fine.



    ------------------------------
    Roberto Innocenti
    ------------------------------