We're reclaiming inactive PDIs to keep them available for active builders. Learn what's changing, who's affected, and how to protect your work. Read More

Orchestration says User not in group

KenX
Tera Expert

Hello Community,

 

Problem : When orchestration executes 'remove user from group' activity, the result says that it couldn't remove the user because the user is NOT a member of the group. However, if I pull that group using a different activity or via ldap browsing or simply looking in AD, all avenues confirm the user IS a member of the group. 

 

Question: What could be causing the incorrect feedback while trying to remove a user from an AD group?

7 REPLIES 7

sandeepdutt
Tera Patron

Hi @KenX ,

Are you running a Flow ?

Thanks,
Sandeep Dutta

Please mark the answer correct & Helpful, if i could help you.

Initially I was running workflow activity "Is User In Group" and then "Remove User From Group". I have tried moving to Flow Designer and the result is the same. 

Ankur Bawiskar
Tera Patron

@KenX 

may be both the groups while removing user and checking group membership are different

did you check and compare?

💡 If my response helped, please mark it as correct and close the thread 🔒— this helps future readers find the solution faster! 🙏

Regards,
Ankur
Certified Technical Architect  ||  10x ServiceNow MVP  ||  ServiceNow Community Leader

Yes. Running the 'is user in group' activity in workflow was showing user was NOT in group. Running the Flow Designer Action showed the user IS in the group. That's why i migrated to Flow Designer but it is still returning a result that the user is not in the group which is part of the confusion.