Robotic Process Automation (RPA)

Robotic Process Automation (RPA)

Come for answers. Stay for best practices. All we’re missing is you.

 View Only

  • 1.  RPA Script working in Studio and not if scheduled

    Posted 05/06/26 09:43 AM
      |   view attached

    Dear all,

    the script (in attachement, where I added a .txt extension to the .wal) runs correctly in debug mode (launched from IBM RPA Studio).

    However, when it is scheduled in unattended mode (on the same machine with the same user account), browser navigation encounters capture errors and unexpected behavior.

    The Chrome browser is opened by the script using the default automation profile.

    Have you ever faced the same issue? Any idea for help?
    Thanks in advance
    Maurizio



    ------------------------------
    Maurizio Caronni
    Senior Project Manager
    Beta 80
    Milano
    3357256907
    ------------------------------

    Attachment(s)

    txt
    VxxxxxxxRPA4Tickets.wal.txt   136 KB 1 version


  • 2.  RE: RPA Script working in Studio and not if scheduled

    Posted 05/07/26 06:56 AM

    Do you have the logs? What error is occurring?



    ------------------------------
    Tarcio Alonso Mota
    Sr. Software Developer
    IBM
    ------------------------------



  • 3.  RE: RPA Script working in Studio and not if scheduled

    Posted 05/20/26 05:49 AM

    Hi,

    I have the same problem since 24th April, after der upgrade to version 30.0.2.0

    Till this date it works perfectly on version 30.0.0.0

    The Bot runs in the project tab says "waiting" in the status.

    The Upcoming bot runs looks fine.

    Computer and computergroup is connected.

    Thanks, Michael



    ------------------------------
    Michael Peinsipp
    ------------------------------



  • 4.  RE: RPA Script working in Studio and not if scheduled

    Posted 05/20/26 07:00 AM

    I think your problem is completely different from Maurizio's.

    I recommend checking the Agent Service logs on your VM for errors.
    When the bot is in a "waiting" state, it is very likely due to a communication failure with the MQ service.

    You can take a look at the troubleshooting section in the documentation, or even open a support ticket with the logs and as much information as possible.



    ------------------------------
    Tarcio Alonso Mota
    Sr. Software Developer
    IBM
    ------------------------------

    Original Message


Related Content