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

CPM issue with interaction context page



When launching multiple interactions in different IE tabs, the content of a custom thread family page is shared between interactions.

Error Messages

Not Applicable

Steps to Reproduce

  1. Create a page which is used to store interaction wide content and promote it to thread family scope in interaction processing.
  2. Launch an interaction which references said thread family page in multiple locations.
  3. Launch a second interaction in another thread. 
  4. Navigate back to the first interaction and observe that the references to the thread family page contain information from the second interaction.

Root Cause

An issue in the custom application code or rules. The threads launched in this custom application do not have the tags looked for when extracting an applicable thread family during thread creation.
Core engine pega platform support is there for associating a thread to thread family automatically when we follow a pattern for thread names; pyNS_[ThreadFamilyName]_XXXX. When a thread name is starting pyNS_, thread family will be set automatically. In this case, pxFamilyName will be set using the identifier which is there between ‘pyNS_’ and the next ’ _’.


Here’s the explanation for the reported behavior: 

The behavior seen is expected given the lack of tags to have a thread family property extracted at thread creation. 

Published March 5, 2016 - 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