{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":22556,"path":"integrate-applications/view-process-jobs-botprocess.md","title":"View the process jobs of a bot process in RPA Hub","bundle":null,"doc_type":null,"release":"australia","body":"\n# View the process jobs of a bot process in RPA Hub\n\nView a list of execution logs of a bot process in RPA Hub.\n\n## Before you begin\n\nCreate a bot process. For more information, see [Configuring a bot process record in RPA Hub](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/create-botprocess.md).\n\nRole 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\n\n## About this task\n\nA process job represents the execution of a bot process on a robot.\n\n## Procedure\n\n1.  Navigate to **All** &gt; **Robotic Process Automation** &gt; **RPA Hub Workspace**.\n\n2.  Select the list icon \\(\\[Omitted image \"rpahublist-icon.png\"\\] Alt text: List icon.\\).\n\n3.  On the **Lists** tab, under **Build**, select **Bot Process**.\n\n4.  Open a bot process to view the related process jobs.\n\n5.  On the **Process Jobs** tab, select the process job that you want to view.\n\n    For more information, see [Process job states in RPA Hub](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/view-process-jobs-botprocess.md).\n\n6.  Open a process job record to view an associated automation log.\n\n7.  In the Automation Logs tab, view the details.\n\n\n**Parent Topic:**[Monitoring automations](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/monitoring-automations-rpa.md)\n\n## Process job form in RPA Hub\n\nUse the Process job form to view a list of the execution logs of a bot process.\n\n<table id=\"table_pyx_mhd_4qb\"><thead><tr><th>\n\nField\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nName\n\n</td><td>\n\nName of the process job.\n\n</td></tr><tr><td>\n\nProcess\n\n</td><td>\n\nName of the associated bot process.\n\n</td></tr><tr><td>\n\nRobot\n\n</td><td>\n\nAssigned robot that is running on the bot process.\n\n</td></tr><tr><td>\n\nState\n\n</td><td>\n\nState of the process job:-   Success\n-   Failed\n-   Running\n-   Skipped\n-   Canceled\n-   Abandoned\n\nFor more information about process job states and their scenarios, see [Process job states in RPA Hub](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/view-process-jobs-botprocess.md).\n\n</td></tr><tr><td>\n\nStorage\n\n</td><td>\n\nStorage location of the logs:-   **Instance**\n-   **Robot Machine**\n\n</td></tr><tr><td>\n\nTriggered By\n\n</td><td>\n\nSource of the trigger.-   **Schedule**- If the automation is triggered via a schedule.\n-   **API**- If the automation is triggered by a flow\n-   **Manual**- If the attended automation is triggered by a user or if the unattended automation is triggered by **Start Process**.\n-   **Embedded Task Automation**- If the attended automation is triggered from the ServiceNow form.\n\nFor more information, see [Embedded Task Automation \\(ETA\\) in RPA Hub](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/integrate-applications/embedded-task-auto-rpa.md).\n\n\n</td></tr><tr><td>\n\nExecution Log Status\n\n</td><td>\n\nStatus on the availability of the execution logs:-   **No Logs**\n-   **Sync in progress**\n-   **Complete**\n\n The available logs are viewed on the RPA Desktop Design Studio.\n\n</td></tr><tr><td>\n\nGraceful Stop\n\n</td><td>\n\nIndicates whether the Graceful Stop is executed or not.If it is marked true, the associated bot process is stopped gracefully instead of stopping abruptly.\n\n</td></tr><tr><td>\n\nStarted At\n\n</td><td>\n\nStart date and time of the process job.\n\n</td></tr><tr><td>\n\nCompleted At\n\n</td><td>\n\nEnd date and time of the process job.\n\n</td></tr><tr><td>\n\nDuration\n\n</td><td>\n\nTime taken to complete the automation.\n\n</td></tr><tr><td>\n\nMessage\n\n</td><td>\n\nAny information or error message returned by the robot.\n\n</td></tr></tbody>\n</table>**Related topics**  \n\n\n[View the process jobs of a bot process in RPA Hub]()\n\n[View process jobs for all bot processes in RPA Hub]()\n\n## Process job states in RPA Hub\n\nA process job represents the execution of a bot process on a robot.\n\n<table id=\"table_olx_3hf_xcc\"><thead><tr><th>\n\nState\n\n</th><th>\n\nScenario\n\n</th></tr></thead><tbody><tr><td>\n\nRunning\n\n</td><td>\n\nWhen a bot process is being executed by a robot, the status of the process job is updated to **Running**.\n\n</td></tr><tr><td>\n\nCanceled\n\n</td><td>\n\nWhen 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**.\n\n</td></tr><tr><td>\n\nSuccess\n\n</td><td>\n\nAfter a bot process is executed successfully by a robot, the process job status is updated to **Success**.\n\n</td></tr><tr><td>\n\nFailed\n\n</td><td>\n\nWhen a bot process execution fails to complete, the process job status is updated to **Failed**.\n\n</td></tr><tr><td>\n\nSkipped\n\n</td><td>\n\nConsider 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**.\n-   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**.\n-   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**.\n-   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**.\n-   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**.\n-   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**.\n\n</td></tr><tr><td>\n\nAbandoned\n\n</td><td>\n\n-   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**.\n-   When a process job is running, the robot state is moved from **Busy** state to any other state.\n\nFor 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.\n\nIn 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**.\n\n\n</td></tr></tbody>\n</table>"}}