-
Feature Request
-
Resolution: Unresolved
-
Major
-
None
-
2.5
-
False
-
-
False
1] What is the nature and description of the request?
The customer is requesting the ability to configure recurring schedules in Ansible Automation Platform (AAP) so that a Job Template can automatically run every 15 minutes between 6:15 AM and 10:45 PM CET, Monday through Friday, without requiring separate schedules or manual intervention.
Currently, in AAP 2.5, while there is an option to set an end time for a schedule, doing so causes the schedule to stop entirely after that time and does not resume on the following day—which prevents users from defining a recurring time window within each day.
2] Why does the customer need this? (List the business requirements here)
-
- The customer has business workflows that must run only during specific business hours (6:15 AM to 10:45 PM CET) on weekdays.
-
- Continuous execution outside of this window could lead to unintended system changes or unnecessary load on the infrastructure.
-
- Manually creating and managing multiple schedules for each weekday introduces operational overhead and increases the chance of configuration errors.
-
- An automatic, time-bound schedule within each day would simplify operations, improve maintainability, and ensure consistent execution of time-sensitive tasks.
- An automatic, time-bound schedule within each day would simplify operations, improve maintainability, and ensure consistent execution of time-sensitive tasks.
3] How would you like to achieve this? (List the functional requirements here)
-
- Introduce support for defining daily time window constraints (start and end times) within a single recurring schedule.
-
- The schedule should:
-
-
- Start execution at a defined time (e.g., 6:15 AM CET) and stop triggering jobs after a defined end time (e.g., 10:45 PM CET).
-
-
-
- Continue this behavior recurringly from Monday to Friday without requiring multiple separate schedules.
-
-
- Ideally, enhance the rrule support in the AAP UI/API to include BYHOUR, BYMINUTE, and other relevant RFC 5545 options to support fine-grained recurring patterns.
-
- Alternatively, provide a user-friendly mechanism in the UI and API to define "Active Hours" for a given schedule.