--- sourceDocument: Brazil Workflow Data Fabric sourceDocumentLink: https://www.servicenow.com/docs/r/integrate-applications Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Workflow Data Fabric ft:clusterId : - crint bundleId : - crint workflow : - Creator --- # View process jobs of a bot process # View the process jobs of a bot process in RPA Hub {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 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](https://www.servicenow.com/docs/Fh5n_jyVL~kis5vxVwxTSQ "In RPA Hub, you can create a bot process configuration record and assign assets to associate it with a bot process. Or you can just save the bot process configuration record, however it won't be associated to a bot process. It remains orphaned."). 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 AllRobotic Process AutomationRPA 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](https://www.servicenow.com/docs/SaRp85ikw2bxyvp6_j~Ysg#process-job-states-rpa "A process job represents the execution of a bot process on a robot."). 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 {#ariaid-title2} Use the Process job form to view a list of the execution logs of a bot process. {#process-job-form__table_pyx_mhd_4qb__entry__2} | 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 {#process-job-form__ul_i33_cyw_2rb} For more information about process job states and their scenarios, see [Process job states in RPA Hub](https://www.servicenow.com/docs/SaRp85ikw2bxyvp6_j~Ysg#process-job-states-rpa "A process job represents the execution of a bot process on a robot."). | | Storage | Storage location of the logs: * Instance * Robot Machine {#process-job-form__ul_pzf_pp1_dzb} | | 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](https://www.servicenow.com/docs/I0zUXsz4veyo~U40rWPMkA "With the embedded task automation feature, trigger attended bot processes (attended automations) from the ServiceNow forms, apart from initiating them from the Attended Robot application."). {#process-job-form__ul_msg_113_pvb} | | Execution Log Status | Status on the availability of the execution logs: * No Logs * Sync in progress * Complete {#process-job-form__ul_m22_hyw_2rb} 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. | [Table 1. Process job form] {#process-job-form__table_pyx_mhd_4qb} **Related tasks** * [View the process jobs of a bot process in RPA Hub](https://www.servicenow.com/docs/SaRp85ikw2bxyvp6_j~Ysg#view-process-jobs-botprocess "View a list of execution logs of a bot process in RPA Hub.") * [View process jobs for all bot processes in RPA Hub](https://www.servicenow.com/docs/x1ZNJfaym7ClC_ppVF6XYg "View a list of execution logs for all bot processes.") ## Process job states in RPA Hub {#ariaid-title3} A process job represents the execution of a bot process on a robot. {#process-job-states-rpa__table_olx_3hf_xcc__entry__2} | 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. {#process-job-states-rpa__ul_qnl_5jf_xcc} | | 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. {#process-job-states-rpa__ul_ktf_j3b_3bc} | [Table 2. Process job state scenarios] {#process-job-states-rpa__table_olx_3hf_xcc} *[\>]: and then