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.

Support Article

A page is submitted twice after passivation is completed



A page is submitted twice after passivation is completed. This page has messages on a property.
 does not occur if on running the tracer.

Error Messages

Not Applicable.

Steps to Reproduce

  1. Create a simple test activity and set a message on a property,TestA using Property-Set-Messages
  2. Create a harness containing a section with another property, TestB
  3. Add an action which refreshes the section and calls another activityThe activity that runs before the refresh should set the TestB property with information regarding the message on the TestA property. It should first check hasMessages on the step page and record the result. It should then obtain the message and should again check hasMessages and record the result. The hasMessages value is true before and after referencing
  4. Wait for passivation to occur. The hasMessage value is false before the referencing and true after referencing

Root Cause

A defect in Pegasystems’ code or rules. The @hasMessages() function returns false after passivation even though a property on the page does have messages. However, since the @hasMessages() function returns false, the messages are not cleared. This eventually results in application returning the same page to the user which submits the page twice. 


Apply HFix-42661. This is only applicable to an environment running on databasestorageversion with a value of 6. To identify this value, check the Dynamic System setting 'database/storageversion'.


Published August 24, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration 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.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us