1] What is the nature and description of the request?

• The customer requests the ability to define a workflow or job template once and create multiple scheduled executions of it. Each scheduled execution should allow specifying inventory, limit, and tag values dynamically, without requiring separate cloned workflow templates.

• Currently, users must clone workflow/job templates and manually associate each clone with different inventory subsets or task tags, leading to inefficiencies in template management and maintenance. The requested feature aims to improve flexibility and reduce redundancy by allowing inventory, limit, and tag overrides in scheduled definitions.

 
2] Why does the customer need this? (List the business requirements here) * Customers managing scheduled operational workflows (e.g., server patching, compliance checks) need to define workflows once and schedule multiple executions against different inventories.

• Updating steps in a workflow currently requires modifying multiple cloned instances. A centralized definition with scheduling flexibility would reduce manual effort and the risk of inconsistencies.
• Cloning templates for different inventory subsets or different task sets (via tags) results in an overcrowded template list, making navigation and management cumbersome.
• Running workflows against new subsets or to perform specific tasks (e.g., audit vs. enforcement) requires creating yet another cloned copy, further compounding inefficiencies.
• The proposed feature would allow customers to easily scale workflow usage without unnecessary duplication, while supporting varied execution logic using tags.

3] How would you like to achieve this? (List the functional requirements here)
 Enhance the schedule definition for workflows and job templates to allow overriding: * Inventory: Users should be able to select an inventory specific to the scheduled run.

• Limit Values: Users should be able to define limits per scheduled execution.
• Tags: Users should be able to specify tags per schedule, allowing different tasks within the playbook to run depending on the schedule context. This supports use cases such as running audits in one schedule and enforcing configurations in another, all from the same template.

Update the UI and API to support these override options when defining schedules.
 Ensure the core execution logic respects these dynamically assigned values during job runs.
 Update relevant documentation to reflect the new scheduling capabilities.
 
4] GitHub Link (if any)
 https://github.com/ansible/awx/issues/15895