Skip to main content

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

Quiesce behavior during high availability upgrades

Updated on May 11, 2022

If additional auto-generated rules were created after you created the export file for auto-generated rules during a high availability upgrade, users might see a server crash recovery message.

For example, the Pega Platform identifies that the user is activated on a Pega Platform server with a code set different from the passivated Pega Platform server. If so, a new session must be created and re-authentication forced.

The code set check is automatic and conservative in forcing the recreation of a new session. To the user, this appears as recovery from the Pega Platform server crash.

  • Previous topic Performing a rolling upgrade
  • Next topic Data management for upgrading and patching highly available systems

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