--- sourceDocument: Australia Workflow Data Fabric sourceDocumentLink: https://www.servicenow.com/docs/r/australia/integrate-applications Release : - australia ft:locale : - en-US ft:publication_title : - Australia Workflow Data Fabric ft:clusterId : - crint bundleId : - crint workflow : - Creator --- # Graceful Stop function # Using Graceful Stop functionality in RPA Hub {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Using Graceful Stop functionality in RPA Hub The Graceful Stop functionality in RPA Hub allows robots to exit automations smoothly by defining secure termination points. This feature is essential for performing clean-up tasks, such as closing applications in use, while maintaining data integrity during automation processes. It is applicable to both assigned robots and those in a robot pool. Show full answer Show less ## Key Features * **Smooth Termination:** Enables robots to finish existing transactions before stopping, preventing data inconsistencies. * **Housekeeping Activities:** Allows RPA developers to perform necessary clean-up tasks, such as closing open applications. * **Enhanced Automation Logic:** Utilizes the GracefulStop component in RPA Desktop Design Studio to ensure that automations complete their current tasks before terminating. * **Robot Pool Compatibility:** Requires the latest Washington DC release Unattended Robot MSI for graceful stopping in robot pools. ## Key Outcomes With Graceful Stop enabled, when a process is stopped, robots will complete all transactions, ensuring that all data is populated correctly in downstream applications. This results in better data integrity and allows developers to manage clean-up tasks effectively. Without this functionality, robots would halt abruptly, risking data loss and complicating post-process management. Graceful Stop functionality provides a capability for robots to exit the automation smoothly. You can define a secure termination point within an automation process. It also enables you to perform clean-up tasks such as closing in-use applications. It is applicable for assigned robots as well as robots in a robot pool. ## Challenges prior to Graceful Stop functionality {#graceful-stop-rpa__section_uss_q11_yxb} * Prior to Graceful Stop, when you select the Stop Process button on a bot process, the robots exit the automation abruptly leading to data inconsistency and data inefficiencies. * RPA developers cannot perform the house-keeping activities. {#graceful-stop-rpa__ul_jsh_1pc_3zb} ## Benefits of Graceful Stop functionality {#graceful-stop-rpa__section_hfw_jfr_bzb} * Data sanity is maintained as the robot completes the existing transaction items. * RPA developers can perform the house-keeping activities, such as, closing the downstream application. {#graceful-stop-rpa__ul_rpp_bpc_3zb} ## How Graceful Stop works {#graceful-stop-rpa__section_tdq_yfr_bzb} Let's consider a shipping order use case that contains 10 order detail records in a spreadsheet. These order details are populated into a downstream application, for example, Shipping Management application. RPA developer builds an automation for this use case in the RPA Desktop Design Studio. Since the spreadsheet has 10 records, queues are used in the automation to synchronise the data to be populated into the Shipping Management application. Each robot picks the work item, performs the logic, and pushes the data into the Shipping Management application. If the bot process is stopped by selecting Stop Process for all or a subset of robots and the Graceful Stop is not enabled, then the robots end the automation execution abruptly. For example, if there are 6 columns in the spreadsheet, the robot stops at column C abruptly, without populating the information in columns D, E, and F. The application which is open, might not be closed. In the RPA Hub, when you enable the Graceful Stop toggle switch in Stop Process section, the data in all the columns (D,E,F) are populated and the downstream application is closed. For more information, see [Stop an unattended bot process in RPA Hub](https://www.servicenow.com/docs/OiHiTzxYwY6KPilFIwHaoQ "Stop the unattended bot process to abort the automation by the selected robot. If robot pool is enabled for a particular bot process, then the execution is stopped for all the robots of the robot pool."). In the RPA Desktop Design Studio, when you use the GracefulStop component in your automation logic, it ensures that the automation is completed. For more information, see [Use the GracefulStop component](https://www.servicenow.com/docs/l1fSQHcuabnbs7FrKhOAIA "Verify that an automation from RPA Hub doesn't stop abruptly by using the GracefulStop component in RPA Desktop Design Studio. With this component, you can define a secure termination point within an automation process and automate housekeeping activities such as closing in-use applications or performing clean-up operations."). It completes the existing work items, populates the data into the downstream application, and helps the developer to perform house-keeping activities such as closing the application. ## New MSI for Unattended Robot {#graceful-stop-rpa__section_azw_j2h_y1c} For the graceful stop functionality to be applicable on robots in a robot pool, upgrade to the latest Washington DC release specific Unattended Robot MSI. For more information, see [Download the RPA applications from RPA Hub](https://www.servicenow.com/docs/AYjii2t9AXSxHzrwecGN3A "Download the Robotic Process Automation (RPA) applications in your Windows machine from RPA Hub as a prerequisite for installing the applications or upgrading them."). If the latest MSI is not installed and if the robot pool is enabled for a particular bot process, then the execution is stopped for all the robots of the robot pool. For these bot processes, you can't use a graceful stop for robots in a robot pool.