*Customer Business Requirement*

Some playbook tasks are not idempotent, and others may require a significant amount of time to complete. When a job fails under these conditions, the customer needs the ability to resume execution from a specific task using the `--start-at-task` option, rather than rerunning the entire playbook.

Although job tags can technically be used to skip tasks, this approach is not practical. In most cases, users cannot predict in advance which task might fail. As a result, they must either modify the playbook to add tags before rerunning the job or proactively insert numerous redundant tags to ensure flexibility. Both approaches create operational overhead and lead to a poor user experience.

If Ansible Automation Platform (AAP) does not provide feature parity with what is available in Ansible Core—such as the ability to resume execution from a specific task—it may discourage customers from adopting or continuing to use the commercial offering. Supporting this capability would improve operational efficiency and strengthen the overall value proposition of the platform.