# Alarm Schedules

**URL:** <https://forum.inductiveautomation.com/t/alarm-schedules/6649>\
**Category:** Ignition\
**Created:** [June 5, 2013, 5:34pm UTC](https://forum.inductiveautomation.com/t/alarm-schedules/6649 "2013-06-05T17:34:09Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![allenr8](https://avatars.discourse-cdn.com/v4/letter/a/e56c9b/32.png) [@allenr8](https://forum.inductiveautomation.com/u/allenr8)\
**Post date:** [June 5, 2013, 5:34pm UTC](https://forum.inductiveautomation.com/t/alarm-schedules/6649/1 "2013-06-05T17:34:09Z")

</div>

The schedules don’t appear to be working for our project. We have two on-call shifts that are 7 days apart. The person that is shown as unavailable is the first one on the list right now, but they are still getting all the calls. Am I missing something?

---

<div class="post-metadata">

**Author:** ![Robert.McKenzie](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/robert.mckenzie/32/4134_2.png) [@Robert.McKenzie](https://forum.inductiveautomation.com/u/Robert.McKenzie)\
**Post date:** [June 11, 2013, 6:44pm UTC](https://forum.inductiveautomation.com/t/alarm-schedules/6649/2 "2013-06-11T18:44:15Z")

</div>

I need a bit more information to know what exactly your problem is. What do you have the schedule set to? Are you using the Repeat/Alternate schedule?

---

<div class="post-metadata">

**Author:** ![allenr8](https://avatars.discourse-cdn.com/v4/letter/a/e56c9b/32.png) [@allenr8](https://forum.inductiveautomation.com/u/allenr8)\
**Post date:** [June 11, 2013, 6:54pm UTC](https://forum.inductiveautomation.com/t/alarm-schedules/6649/3 "2013-06-11T18:54:24Z")

</div>

The schedules are set on a weekly rotation so one week on one week off. See the attached screenshot.

I have one week called week A that is the picture and another schedule called Week\_B that is the next schedule.

The operator gets calls even when he is “off” schedule.

 ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/d/d11aa0842a2e84049979e2c2e4716b3e68fda9bf.PNG)

---

<div class="post-metadata">

**Author:** ![Robert.McKenzie](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/robert.mckenzie/32/4134_2.png) [@Robert.McKenzie](https://forum.inductiveautomation.com/u/Robert.McKenzie)\
**Post date:** [June 11, 2013, 9:47pm UTC](https://forum.inductiveautomation.com/t/alarm-schedules/6649/4 "2013-06-11T21:47:50Z")

</div>

So you are saying that he was receiving calls on last Tuesday (The 4th)? Is that user set to be on this Week\_A Schedule, or are they on the “Always” Schedule, or something else?

---

<div class="post-metadata">

**Author:** ![allenr8](https://avatars.discourse-cdn.com/v4/letter/a/e56c9b/32.png) [@allenr8](https://forum.inductiveautomation.com/u/allenr8)\
**Post date:** [June 11, 2013, 10:32pm UTC](https://forum.inductiveautomation.com/t/alarm-schedules/6649/5 "2013-06-11T22:32:42Z")

</div>

There is one operator on Week\_A and one on Week\_B. In the roster they are each listed three times. There are some people below them who are on the always.

John  
John  
John  
Joe  
Joe  
Joe

John always receives the call first no matter what the date whether he is available or not.

---

<div class="post-metadata">

**Author:** ![James.Lorenz](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/james.lorenz/32/3290_2.png) [@James.Lorenz](https://forum.inductiveautomation.com/u/James.Lorenz)\
**Post date:** [June 12, 2013, 11:50pm UTC](https://forum.inductiveautomation.com/t/alarm-schedules/6649/6 "2013-06-12T23:50:15Z")

</div>

I was able to replicate this scheduling issue, I’ll pass this issue on to the developers and hopefully a fix will make it into 7.6.2.

---

<div class="post-metadata">

**Author:** ![allenr8](https://avatars.discourse-cdn.com/v4/letter/a/e56c9b/32.png) [@allenr8](https://forum.inductiveautomation.com/u/allenr8)\
**Post date:** [June 14, 2013, 5:21pm UTC](https://forum.inductiveautomation.com/t/alarm-schedules/6649/7 "2013-06-14T17:21:41Z")

</div>

Any idea when that stable release will be done?
