Orchestration says User not in group

[KenX]

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?

[KenX]

Here is what has happened since switching to Flow Designer. The activity never finishes looking up the user. This is after approximately 10 to 14 minutes waiting.

But it prints the following results...

[Tanushree Maiti]

Hi @KenX 

Refer: Remove User from Group AD activity 

• Verify if AD and ServiceNow are synchronized. The ServiceNow cache might temporarily retain the membership status before AD updates fully propagate
• Refer: https://www.servicenow.com/community/servicenow-ai-platform-forum/flow-issue-running-the-ad-remove-u...
•  

[KenX]

The two are synchronized in the sense that after I manually created the user, there was about a 30 minute delay for reconciliation and then automation was successfully locating the user account. Group membership at this point was also up-to-date when manually retrieved.