Robotic Process Automation (RPA)

 View Only
  • 1.  orchestrator process via API bot never starts

    Posted Wed June 15, 2022 03:25 PM
    Right now we are trying to run a robot via the new api(https://www.ibm.com/docs/en/rpa/21.0?topic=api-starting-bot-in-orchestrator-process-via) but it has not been possible.

    the api creates the instance but the robot never starts, it stays in pending.

    I am almost sure that the configuration is correct, since if I send data to the queue through another robot, the robot starts.



    the problem seems to be with the api, could it be that I am missing something?

    ------------------------------
    felipe Andres Barrera Torres
    ------------------------------


  • 2.  RE: orchestrator process via API bot never starts

    Posted Thu June 16, 2022 11:59 AM
    Hi felipe,

    I have experienced this.  I've found the bot runs if my target computer is a VM, but it stays in a pending state if my target computer is my Laptop.  It maybe something to do with the credentials of the computer.   I suggest you schedule the bot to run on your target computer.  If that works, in my experience it will also work through the API.

    ------------------------------
    NIGEL CROWTHER
    ------------------------------



  • 3.  RE: orchestrator process via API bot never starts

    Posted Thu June 16, 2022 03:13 PM

    Hi Felipe,

    Can you access the computer page? if so verify the computer you set up for the process, look at the "Queue runtime percentage" field, the value for this field should be higher than 0%.

    Also verify if that computer has a credential, the process instances will take over the user session of the machine.



    ------------------------------
    Daniel de Oliveira Koda Fiorentini
    ------------------------------



  • 4.  RE: orchestrator process via API bot never starts

    Posted Fri June 17, 2022 09:58 AM

    Thanks Daniel,

    in effect they are configured, I sent you a photo.


    also if I run with shedule or send something to the queue with another robot or with the agent api (localhost:8099/<scripts/<scriptname>) the robot starts without problem.


    the problem seems to be with the new api, it creates the instance in the control center but the instance never starts!!



    ------------------------------
    felipe Andres Barrera Torres
    ------------------------------



  • 5.  RE: orchestrator process via API bot never starts

    Posted Fri June 17, 2022 10:10 AM

    Hey Felipe,

    In the control panel of that process the computer is online?(to verify access the process page, find yuor process and in the options button choose control panel).

    If the Api does create the instance I dont think the problem is in the API, because is not the api who runs the orchestration.

    In studio you can look at the Help tab, and in the Studio / Agent logs, and verify if the process is being fetched. (search for the word "Fetch").

    Also is a good idea to see if the step of your process is not paused, you can see that in the control panel of your process.



    ------------------------------
    Daniel de Oliveira Koda Fiorentini
    ------------------------------



  • 6.  RE: orchestrator process via API bot never starts

    Posted Fri June 17, 2022 11:27 AM
    again thank you very much daniel,

    yes indeed, in the control panel it shows 1 computer 1 runtime

    and the step is not paused

    also in the log there was nothing with fetch

    ------------------------------
    felipe Andres Barrera Torres
    ------------------------------



  • 7.  RE: orchestrator process via API bot never starts

    Posted Mon June 27, 2022 10:29 AM

    Hi Felipe,

    can you please download the computer certificate from the Computer page, and install it on the machine where the process needs to run?

    Regards,



    ------------------------------
    Daniel de Oliveira Koda Fiorentini
    ------------------------------



  • 8.  RE: orchestrator process via API bot never starts

    Posted Mon June 27, 2022 03:24 PM
    Did you manage to fix it?
    If not, I suggest opening a support ticket.

    ------------------------------
    Joba Diniz
    Product Manager
    IBM
    ------------------------------