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

Race condition in Cases

SA-20119

Summary



When two service requests are served generating two cases at the same time, a race condition coupled to their datapages is observed. The race condition occurs in the SLA processing of the cases which reference a thread level page to determine routing behavior. The cases route to the same operator even though this is suppose to be prohibited by the routing logic. The reason appears to be stale page data.


Error Messages



Not applicable


Steps to Reproduce

  1. Setup a service integration to create cases in the Pega platform.
  2. Configure a wait shape in the flow that assigns the case to an operator based on the content of potential assignees in a datapage.
  3. Observe that two cases are routed to the same operator.


Root Cause



The behavior indicated a stale datapage on the second reference and as such a page-remove of the datapage was added prior to the reference in question to ensure freshness. 

Resolution



Perform the following local-change: 

Add a page-remove of the datapage prior to the reference receiving the stale response.

Suggest Edit

Published February 26, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

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

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