Issue: The client would raise a concern saying wherein they would be unable to deactivate the user even though they have been removed it from every automation.
PFB the screenshot attached of the user:
PFB the screenshot of the card from where the user is already replaced from another user:
Solution: Here the scenario could be that even if the user is replaced in the automation but if the automation is soft Unpublished then too the user would not be de activated, what we need to do here is we need first republish the automation and then unpublish it which would allow us to deactivate the user.
If there are multiple such automations then please follow this process to replace the users from backend: User Replacement API for User Deactivation
