Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Robotic Automation example: Shutting down emulator processes

Updated on September 10, 2021

For best results, all Pega Robotic Automation solutions that include a text adapter should also include logic that makes sure that no emulators are running before you start the robotic automation.

Some emulators do not shut down entirely and instead leave processes running. If processes are still running and your automation starts, the automation could connect to the wrong process and not work as designed.

To avoid this issue, add logic to the beginning of your automation to search for and shut down any running emulators. The following example solution provides an example of a solution that shuts down any Rumba emulators, and then starts Pega Robot Runtime.

Example solution for shutting down Rumba processes

Example solution for shutting down Rumba processes

  • Previous topic Robotic Automation example: Selecting all entries in a list box that is on a webpage
  • Next topic Robotic Automation example: Using the ICA file template for load balancing using the ZDC


Robotics System Architect Robotic Process Automation

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us