Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Rolling back a problematic deployment

Suggest edit Updated on April 5, 2022

In the event of a problematic deployment, the first goal is to prevent further issues from occurring. Then you can roll back the deployment and restore your system to a state that was previously known to be working.

Do the following steps:

  1. Ensure that no new operators can access the problematic application. You can temporarily disable access to the entire system. For more information, see How to temporarily disallow new interactive logins with a Dynamic System Setting.

  2. Roll back the problematic rules changes. You can roll back changes by updating the access group for your application and specifying the previous version of your application.

Result: Roll back the data instances that you changed to their previous version. To roll back data changes, use the prpcServiceUtils command line utility. For more information, see Rolling back and committing tracked data. This process replaces those modified data instances with their prior definition, rolling back your data changes to the last known, good state.
Did you find this content helpful? YesNo

Have a question? Get answers now.

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

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us