Assignment Group Already In Use

[TcKiddco]

I am trying to create a new assignment group for our organization.  This assignment group is the first time it was to be used.  Several other assignment groups beginning with the same prefix as the one I am trying to create have been successfully created.  However, when I attempt to create this new assignment group, "ASG-NETOPS-POWLA-POWER.   The system feedback received is as follows:  "The group name is alrady in use, please create another group name"  How can this assignment group already be in use if I am creating it for the first time?   Where can I locate this assignment group that is already in use?  When attempting to retrieve all the assignment groups, the system does not list this assignment group among the ones which have already been successfully created. 

[clarksal · Accepted solution]

You can use the assignment group look up table to see if the assignment group name already exists and if it does you can modify the naming convention accordingly.  

[G Ponsekar · Accepted solution]

Hi @TcKiddco ,

When you receive the error "The group name is already in use, please create another group name," it indicates that a group with that exact name exists in the database, even if it does not appear in your standard list view. This most commonly happens because the group is inactive

• In the Application Navigator, type sys_user_group.list and press Enter. This will open the list view for the Groups table.
• Click the filter icon (the funnel).
• Set the filter condition to: Name is ASG-NETOPS-POWLA-POWER.
• Run the filter. This should return the group record, regardless of whether it is active or not.

If I could help you with your Query then, please hit the Thumb Icon and mark as Correct !!

Thanks, GP

[M Iftikhar · Accepted solution]

Hi @TcKiddco 

You’re seeing this error because ServiceNow enforces unique group names, including those that are inactive or hidden.
To confirm:

• Navigate to sys_user_group.list and search with the exact group name.

• If it exists but is inactive, you can either reactivate it or choose a new unique name.

This avoids creating duplicates and keeps group data clean.

I came across a similar discussion on the community discussing this same error you may find it helpful:
https://www.servicenow.com/community/sysadmin-forum/duplicate-group-names/td-p/3382274

Thanks & Regards,
Muhammad Iftikhar

If my response helped, please mark it as the accepted solution so others can benefit as well.

[svirkar420 · Accepted solution]

@TcKiddco , You can proceed with the 1st option, Delete the existing assignment group and create a new one. 

2. Update the existing group as you intended while creating it at the first place.

You can go with both option it is you to decide what do you want to proceed with. (I would suggest you to go with 2nd option it is considered as best practice).

Also, you can accept more than one answer as solution.

@TcKiddco , If this solution helped you Please Mark this solution as accepted and helpful as it will be helpful for other users as well.
Best Regards.
Saurabh V.

[M Iftikhar · Accepted solution]

Hi @TcKiddco 

You’re seeing this error because ServiceNow enforces unique group names, including those that are inactive or hidden.
To confirm:

• Navigate to sys_user_group.list and search with the exact group name.

• If it exists but is inactive, you can either reactivate it or choose a new unique name.

This avoids creating duplicates and keeps group data clean.

I came across a similar discussion on the community discussing this same error you may find it helpful:
https://www.servicenow.com/community/sysadmin-forum/duplicate-group-names/td-p/3382274

Thanks & Regards,
Muhammad Iftikhar

If my response helped, please mark it as the accepted solution so others can benefit as well.