View the process jobs of a bot process in RPA Hub

  • Release version: Australia
  • Updated March 12, 2026
  • 4 minutes to read

    • View a list of execution logs of a bot process in RPA Hub.

    Before you begin

    Create a bot process. For more information, see Configuring a bot process record in RPA Hub.

    Role required: sn_rpa_fdn.rpa_release_manager, sn_rpa_fdn.rpa_support_user, sn_rpa_fdn.rpa_developer, sn_rpa_fdn.rpa_business_user, or sn_rpa_fdn.rpa_admin

    About this task

    A process job represents the execution of a bot process on a robot.

    Procedure

    1. Navigate to All > Robotic Process Automation > RPA Hub Workspace.
    2. Select the list icon (List icon.).
    3. On the Lists tab, under Build, select Bot Process.
    4. Open a bot process to view the related process jobs.
    5. On the Process Jobs tab, select the process job that you want to view.
      For more information, see Process job states in RPA Hub.
    6. Open a process job record to view an associated automation log.
    7. In the Automation Logs tab, view the details.

    Process job form in RPA Hub

    Use the Process job form to view a list of the execution logs of a bot process.

    Table 1. Process job form
    Field Description
    Name Name of the process job.
    Process Name of the associated bot process.
    Robot Assigned robot that is running on the bot process.
    State State of the process job:
    • Success
    • Failed
    • Running
    • Skipped
    • Canceled
    • Abandoned

    For more information about process job states and their scenarios, see Process job states in RPA Hub.
    Storage Storage location of the logs:
    • Instance
    • Robot Machine
    Triggered By Source of the trigger.
    • Schedule- If the automation is triggered via a schedule.
    • API- If the automation is triggered by a flow
    • Manual- If the attended automation is triggered by a user or if the unattended automation is triggered by Start Process.
    • Embedded Task Automation- If the attended automation is triggered from the ServiceNow form.

      For more information, see Embedded Task Automation (ETA) in RPA Hub.
    Execution Log Status Status on the availability of the execution logs:
    • No Logs
    • Sync in progress
    • Complete

    The available logs are viewed on the RPA Desktop Design Studio.
    Graceful Stop Indicates whether the Graceful Stop is executed or not.

    If it is marked true, the associated bot process is stopped gracefully instead of stopping abruptly.
    Started At Start date and time of the process job.
    Completed At End date and time of the process job.
    Duration Time taken to complete the automation.
    Message Any information or error message returned by the robot.

    Process job states in RPA Hub

    A process job represents the execution of a bot process on a robot.

    Table 2. Process job state scenarios
    State Scenario
    Running When a bot process is being executed by a robot, the status of the process job is updated to Running.
    Canceled When a bot process execution is canceled manually, the process job status is updated to Canceled.

    If Bot process 1 is already executing, and Bot process 2 with force start enabled is triggered, then the process job status of Bot process 1 is updated to Canceled, and the process job status of Bot process 2 is updated to Running.
    Success After a bot process is executed successfully by a robot, the process job status is updated to Success.
    Failed When a bot process execution fails to complete, the process job status is updated to Failed.
    Skipped Consider the following scenarios when more than one bot processes are triggered for the same unattended robot:
    • If Bot process 1 is already executing and Bot process 2 with force start disabled is triggered, then the process job status of Bot process 2 is updated to Skipped.
    • If two bot processes, BP1 and BP2, are scheduled to run on the same robot at the same time and BP2 has lower priority (higher priority order number), then the process job status of BP2 is updated to Skipped.
    • If two bot processes, BP1 and BP2, with the same priority order are scheduled to run on the same robot at the same time, then only one of the bot process would be selected randomly for running and the process job status of the other one is updated to Skipped.
    • If Bot process 1 is triggered and robot is waiting to login, and in the mean time Bot process 2 is triggered, then process job status of Bot process 2 is updated to Skipped.
    • The Start process action is invoked for Bot process 1. Until the execution starts, if other bot processes are triggered then the process jobs of all other start process requests are updated to Skipped.
    • When a robot comes back to responsive state, it will start to receive start process requests that were triggered when the robot was in the unresponsive state. The latest request which falls under the configured threshold is updated to Running and all the older requests are updated to Skipped.
    Abandoned
    • For any robot type, if a bot process was previously executing and the process job status was not updated to Completed, and a new process job is created, then the status of the previously executing process job is updated to Abandoned.
    • When a process job is running, the robot state is moved from Busy state to any other state.

      For example, when a process job is executing locally in the robot machine, a robot may fail to update RPA Hub with its heartbeat call due to network failure, certificate authentication failure, machine user profile corruption, and so on.

      In all such scenarios, when the robot calls the RPA Hub after an interruption, and then updates its status from Busy or Disconnected to Available, then the status of the last known process job is changed to Abandoned.