Support Article
Case wide SLA - CallFlow action leads to stage inconsistency
SA-6960
Summary
When SLA is configured for the case type (case wide SLA) it causes normal case flow exception. After SLA is triggered, "Reconcile inconsistency in stage processing" link is displayed.
Similar behavior is observed for the step SLA.
Error Messages
Not Applicable
Steps to Reproduce
1. Create new case type and on Stage1 define Step1.
2. For case type setting in Details tab, configure SLA in Goals and deadline settings.
3. Set 1 minute SLA for the Goal and select Call Flow option.
4. Create new Flow and replace assignment shape with Utility and configure this shape to call new action.
5. For this action, configure step as Log-Message, InfoForced and type the message you want to see on console.
6. Perform the same action, flow and Goal and then case type.
7. Create instance of this Case type and wait on 1st step – UI is not needed.
8. After some time, set in Goal + ServiceLevelEvents Agent specified time. You will see your message set for the action in the flow called once SLA is triggered
9. Refresh your new instance (Actions > Refresh or Other Actions > Refresh depending on your step or stage configuration). You will see Reconcile inconsistency in stage processing link
Root Cause
The root cause of this problem is a defect in Pegasystems’ code/rules to pass the ID for the flow (BUG-192785).
Resolution
This issue is resolved in Pega 7.1.8.
Published January 31, 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.