Inconsistent Behavior SNC.OnCallRotation and OnCallRotation()
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2025 09:00 AM
Hi Everyone
We have a workflow to notify on-call users regarding their shifts, when an high impact incident is raised, also we have an oncall portal which allows users to see their current shift and the primary and secondary contact, however the flow and the portal are failing intermittently, originally we were using SNC.OnCallRotation(), however we were notified in a separate case this class is deprecated, for this reason we switched to OnCallRotation(), after this update we noticed the behavior is very inconsistent and unpredictable between both SNC.OnCallRotation() and OnCallRotation(), here are a few examples:
1. Sometimes SNC.OnCallRotation will bring an escalation plan for a group while OnCallRotation will not and viceversa
2. Sometimes the escalation plan will change in size for example for a particular group with the exact same parameters, for example the escalation Plan size is 2 if it's obtained using OnCallRotation() and 4 when using SNC.OnCallRotation
3. getEscalateeAt will fail with OnCallRotation but will work with SNC.OnCallRotation
We opened a Now Support Case but were hoping anyone who have had the same situation can help us
Thank you