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
- Setup a service integration to create cases in the Pega platform.
- Configure a wait shape in the flow that assigns the case to an operator based on the content of potential assignees in a datapage.
- 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.
Published February 26, 2016 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.