Empty dynamic groups created via App Discovery cannot be deleted

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Users may encounter the following issues when managing groups in the DX Unified Infrastructure Management Operator Console:

*   Dynamic groups created via **App Discovery** (e.g., using `UserTag1` or `UserTag2`) remain in the inventory even when they contain zero members.
*   The **Delete** option is missing from the 'three dots' menu for these groups.
*   Selecting **Edit** on these auto-created groups may cause the Operator Console UI to hang or lock up, requiring a session restart.

Environment

• DX Unified Infrastructure Management (all versions)

Cause

Groups created by App Discovery rules are considered auto-managed. Their lifecycle is controlled by the discovery process rather than manual user intervention. 

This issue typically occurs when robots are deleted from the inventory after the server is decommissioned. Because the robot never responds during the delete, the discovery server does not trigger the automatic deletion of the associated group, leaving it orphaned in the database.

 

Resolution

Since these groups are managed by discovery logic, they must be cleared by triggering that logic. Use one of the following workarounds to remove the orphaned groups.

• Method 1: The 'Test Robot' Trigger
  This method forces the discovery server to see a transition from 'tagged' to 'untagged' for the specific group name.
  1. Identify the exact UserTag value used by the empty group.
  2. Deploy or select a temporary **test robot** in the environment.
  3. Configure the test robot with the **UserTag** that matches the empty group.
  4. Wait for the discovery cycle to complete and verify the test robot appears as a member of the group in the Operator Console.
  5. Remove the UserTag from the test robot and **restart the robot service**.
  6. Once the robot reports back without the tag, the discovery server will identify that no active members remain for that tag and auto-delete the group.
• Method 2: Refresh App Discovery Rules
  If multiple empty groups exist, refreshing the App Discovery configuration can force a rebuild of the group containers.
  1. In the Operator Console, navigate to the **App Discovery** configuration.
  2. Locate the rule responsible for the UserTag grouping.
  3. **Disable** the rule and save the configuration.
  4. Wait 30 seconds, then **Re-enable** the rule and save again.
  5. This action triggers a re-evaluation of all active tags in the database and should remove containers that no longer have valid members.