on call scheduling question / issue

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2022 07:57 PM
Hi Everyone
I am looking for some help with the on-call scheduling functionality.
The way we have it set up is as such;
We have an On-Call Schedule set up for a Resolver group.
In this schedule we have a primary and secondary roster, with members of each. Our telephone system uses this to route the calls. If the currently active person in the primary roster is busy or doesn't answer, it then bounces to the currently active person in the secondary schedule.
all good so far.
However if we wanted to replace someone for a day, let's say the primary person was sick and we had to change that person for someone else - we are getting some weird behaviour in the following circumstances:
I had to re-do the screenshots so just ignore that the dates change between them
let's just say Josh is sick:
I click on his name and select "manage shift"
I change it to Lachlan for a day or so
Now when i go back to the calendar, it's showing Peter twice.
If i click on the primary shift, it shows me ALL the members of the group are now in the primary roster
If you check the group details on a day with no coverage, it looks correct:
However, if you go to the on-call schedules view, it does show correctly for who is currently on call if there is coverage in place (this is on day that looks wonky on the calendar, it looks ok here):
This is in pre-production at the moment, so i cant really check who it's actually going to call - but can anyone explain the behaviour above and why it is doing what it is doing? This module is fairly new to me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-24-2023 02:41 AM
Hi @Kai Tingey
Did you managed to get this worked?
I'm seeing the same problems with our On-Call Scheduling.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-24-2023 05:36 AM
Hi Koen,
Yes we did. I had to raise a ticket with Hi support.
in the end the issue was related to all these affected users have 'Resource Management Schedule' as their schedule in user record
To resolve go into sys_user table and change the view to "resource manager"
find your affected users and see if they have "resource management schedule" set as their schedule. if so, clear it and then see if that resolves the issue.