An overnight shift with a daily rotation is rotating to next person at midnight instead of at 8:30 in the morning.

[Cynthia L_]

Our daily overnight shift is 8:30 a.m. to 8:30 a.m the next day. At 8:30 a.m. it is supposed to rotate to the next staff member.  After the Madrid update, it rotates at midnight instead of at 8:30 in the morning. 

If we use a weekly schedule it honors the overnight shift and does rotate to the next staff member on the correct time but the team does not want the staff member to be oncall all week. 

Does anyone have any thoughts on how to fix this?

[Sheila Llewelly]

Hi, Cynthia

I have not personally run into this, but I was reading the release notes in Madrid and it may have your mitigation. "To enable the legacy behavior, create thecom.snc.on_call_rotation.coverage.rota_times_only hidden property. By default, this property is set to true and the coverage on the on-call calendar is enabled for shift schedule. For the legacy behavior, set this property to false."

https://docs.servicenow.com/bundle/madrid-release-notes/page/release-notes/it-service-management/on-...

Good luck and be sure to let me know if it helps!

[Cynthia L_]

Thanks for the information.  I have been reviewing but our system does not seem to be setup in the out-of-the-box way.  

[Cynthia L_ · Accepted solution]

There is a new system property introduced in London - "com.snc.on_call_rotation.factor_daily_rotation_interval_all_day". For rotation to happen, it should have value as false from what I gather from research and as per this documentation:
https://docs.servicenow.com/bundle/london-it-service-management/page/administer/on-call-scheduling/r...