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

Issue with thread and page clean up when a thread is reused



The existing Clipboard threads are reused for a new case once the maximum threads is reached. While reusing the existing case type, the existing user pages and thread level data pages are not flushed out which causes data issues.

Error Messages


Not Applicable


Steps to Reproduce

Configure the maximum number of tabs on the portal to use the existing threads when the maximum number of documents are opened. This can be made by changing the maximum tabs to required value on the Pyportalcontent section. 


This behavior is as per the Pega product design.


Here’s the explanation for the reported behavior: 
The old thread is cleaned up when the DoClose activity is invoked once the maximum number of threads is reached on the out-of-the-box portal. This inturn invokes the pzDocumentCleanup activity at 8th step and deletes the thread.
The above operation does not occur on the custom portal. As a result, user must delete the old thread by invoking the DoClose activity after the maximum number of threads is reached.



Published August 19, 2019 - 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