--- sourceDocument: Zurich IT Operations Management sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/it-operations-management Release : - zurich ft:locale : - en-US ft:publication_title : - Zurich IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Automation opportunity sub-groups # Automation opportunity sub-groups {#ariaid-title1} * Release version: Zurich * * Updated August 11, 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 Zurich release of LEAP, large automation opportunities with over 150 incident records can be subdivided into smaller, more manageable sub-groups. This approach addresses the challenge of overly lengthy and imprecise resolution steps that arise from grouping diverse but related incidents together. By breaking down large opportunities, ServiceNow customers can achieve more granular, relevant, and effective incident resolutions. Show full answer Show less ## Key Features * **Sub-group recommendations:** The Action Insights panel on the automation opportunity details page provides suggestions to create sub-groups for opportunities containing large volumes of records. * **Example of sub-grouping:** A large automation opportunity with 300 password reset incidents could be split into sub-groups such as VPN password resets, Active Directory account lockouts, and SSO token expiry, each with tailored resolution steps. * **Automatic reorganization:** During scheduled LEAP analysis reruns, clusters are automatically reorganized based on updated incident patterns. Existing artifacts remain linked to new automation opportunities rather than being overwritten, ensuring continuity. * **Artifact handling during reorganization:** * Resolution steps are appended to matching new opportunities, with users able to keep or regenerate them. * Playbooks remain active and linked, preserving configurations and execution history. * Knowledge base articles and problem records retain their associations. * Opportunities without any artifacts after reorganization are marked as deactivated. ## Benefits * Delivers more focused and contextual resolution steps, improving precision. * Enables targeted solutions for similar but distinct issues within large incident sets. * Enhances incident resolution efficiency and effectiveness. * Supports operational efficiency by reusing prior resolution artifacts when appropriate. 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 so that 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/TIty6Nx8zOdGcMawz3VAEA "Large automation opportunities in LEAP are broken into smaller, more manageable sub-groups to support focused and contextual incident resolution steps.").