--- sourceDocument: Australia IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management Release : - australia ft:locale : - en-US ft:publication_title : - Australia IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Automation opportunity sub-groups # Automation opportunity sub-groups {#ariaid-title1} Release version: Australia Updated November 5, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Automation opportunity sub-groups In the LEAP system, large automation opportunities with numerous records---typically over 150---can produce lengthy and imprecise resolution steps. To enhance precision and manageability, these large opportunities can be subdivided into smaller, more focused sub-groups. This approach results in more targeted and relevant incident resolutions, improving the overall effectiveness of automation efforts. Show full answer Show less ## Key Features * **Sub-group creation:** The Action Insights panel on the automation opportunity details page recommends breaking down large opportunities into smaller sub-groups based on incident types. * **Example of sub-grouping:** For instance, a large set of 300 password reset incidents might be split into sub-groups such as VPN password resets, Active Directory account lockouts, and SSO token expiries, each with tailored resolution steps. * **Automatic reorganization:** During scheduled LEAP analysis reruns, clusters are reorganized automatically to reflect updated incident patterns. Existing resolution artifacts are preserved and linked to the new clusters rather than overwritten. * **Artifact management during reorganization:** * Resolution steps are appended to matching new automation opportunities, with users able to retain or regenerate them. * Playbooks, knowledge base articles, and problem records remain active and linked to the new opportunities, preserving configurations and histories. * Opportunities without any linked artifacts after reorganization are deactivated. ## Key Outcomes * More focused and contextual resolution steps tailored to specific incident sub-groups. * Enhanced targeting of similar issues, leading to improved incident resolution quality. * Better management and operational efficiency for large automation opportunities. * Reuse of prior resolutions where applicable, saving time and effort. Large automation opportunities in LEAP can be broken into smaller, more manageable sub-groups to achieve more granular and accurate incident resolution. Large automation opportunities with over 150 records tend to generate overly lengthy resolution steps that lack precision and focus. These opportunities often represent a collection of related problems and issues that should be subdivided to produce more targeted and relevant solutions. Breaking them into smaller sub-groups lets users obtain more refined resolutions for recurring issues. The Action Insights panel on the automation opportunity details page offers recommendations to create these sub-groups for opportunities containing large record volumes. ## Sub-grouping example {#automation-opportunity-sub-groups__sub-grouping-example} A large automation opportunity containing 300 password reset incidents might include a mix of VPN password resets, Active Directory account lockouts, and SSO token expiry. While these are all password-related, each requires different resolution steps. LEAP displays suggestions for breaking the automation opportunity into three sub-groups. Each group receives targeted resolution steps --- for example, one sub-group with VPN-specific steps, another with AD unlock procedures, and a third with SSO token refresh instructions. ## Automatic reorganization {#automation-opportunity-sub-groups__automatic-reorganization} During scheduled LEAP analysis reruns, clusters are automatically reorganized based on newly observed incident patterns. LEAP preserves existing artifacts and links them to updated automation opportunities rather than overwriting them. The following table describes how each artifact type is handled during reorganization: {#automation-opportunity-sub-groups__automatic-reorganization__entry__2} | Artifact | Behavior during rerun | |-|-| | Resolution steps | Appended to the new matching automation opportunity. Users can keep the existing steps or select Regenerate to create fresh ones. | | Playbooks | Remain active and are linked to the new matching automation opportunity. Existing playbook configurations and execution history are preserved. | | Knowledge base articles | Remain active and retain their association with the automation opportunity. | | Problem records | Remain active and are linked to the new matching automation opportunity. | [Table 1. Artifact behavior during reorganization] Automation opportunities that no longer have any associated artifacts after reorganization are marked as deactivated. Opportunities that contain resolution steps, playbooks, or other artifacts remain active and are linked to newly identified matching automation opportunities. For example: An automation opportunity for "email delivery failures" has resolution steps and a playbook created in the previous analysis run. When LEAP reruns the analysis and reorganizes clusters, this opportunity is matched to a new cluster. The existing resolution steps are appended to the new automation opportunity. The user can review the appended steps and decide whether to keep them or regenerate new ones based on the updated cluster data. ## Benefits of sub-grouping {#automation-opportunity-sub-groups__benefits-of-sub-grouping} * Provides more focused and contextual resolution steps * Offers more targeted solutions for similar issues * Improves incident resolution * Enables more effective management of large automation opportunities * Supports operational efficiency by reusing prior resolutions where appropriate For detailed steps, see [Create sub-groups for automation opportunities](https://www.servicenow.com/docs/tDOND7YuVRjrbqXvDtF1XQ "Large automation opportunities in LEAP are broken into smaller, more manageable sub-groups to support focused and contextual incident resolution steps.").