# Template Schedule Exceptions

**URL:** <https://forum.ansible.com/t/template-schedule-exceptions/39915>\
**Category:** Get Help\
**Tags:** module, awx\
**Created:** [January 29, 2025, 10:14pm UTC](https://forum.ansible.com/t/template-schedule-exceptions/39915 "2025-01-29T22:14:38Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bmbufalo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/bmbufalo/32/295_2.png) [@bmbufalo](https://forum.ansible.com/u/bmbufalo)\
**Post date:** [January 29, 2025, 10:14pm UTC](https://forum.ansible.com/t/template-schedule-exceptions/39915/1 "2025-01-29T22:14:38Z")

</div>

How do you create Job Template Schedule Exceptions so that a job that is scheduled to run hourly will not run from 2:00 am and 3:00 am? I can’t seem to find a way in the UI.

---

<div class="post-metadata">

**Author:** ![trippinnik](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/trippinnik/32/4308_2.png) [@trippinnik](https://forum.ansible.com/u/trippinnik)\
**Post date:** [February 25, 2025, 3:18pm UTC](https://forum.ansible.com/t/template-schedule-exceptions/39915/2 "2025-02-25T15:18:28Z")

</div>

any solution to this? I don’t understand why AWX isn’t using cron. it’s pretty lacking in this area.

---

<div class="post-metadata">

**Author:** ![bmbufalo](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/bmbufalo/32/295_2.png) [@bmbufalo](https://forum.ansible.com/u/bmbufalo)\
**Post date:** [February 25, 2025, 3:36pm UTC](https://forum.ansible.com/t/template-schedule-exceptions/39915/3 "2025-02-25T15:36:06Z")

</div>

Unfortunately, no. What I did was instead create five jobs that ran as follows:

1. Every two hours, starting at 1 a.m., which captures all odd hours of the day.
2. Every 12 hours, starting at 6 a.m.
3. Every 12 hours, starting at 8 a.m.
4. Every 12 hours, starting at 10 a.m.
5. Every 24 hours, starting at 2 p.m.

This effectively bypasses the 2 a.m. maintenance window. However, I still have some jobs that run during that time at an interval less than hourly, which fail. Therefore, a solution that allows me to exclude a specific timeframe would be more optimal and highly desirable.

---

<div class="post-metadata">

**Author:** ![trippinnik](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/trippinnik/32/4308_2.png) [@trippinnik](https://forum.ansible.com/u/trippinnik)\
**Post date:** [March 3, 2025, 9:19pm UTC](https://forum.ansible.com/t/template-schedule-exceptions/39915/4 "2025-03-03T21:19:03Z")

</div>

This is what we kind of came up with as well. It’s not ideal in terms of management and is disappointing