We have two authentication services setups, the service activity has been written in such a way that even if the operator exists, they remove the current access group and add the required access based on the authentication service. One thing to say is App2 was released into prod after App1 and there are users who are common to both the applications. For these types of users [in order]
When they log in to App2 (works properly).
When they log in to App1 (works properly).
When they try to access App2 (doesn't work as expected). Logs the user into the App1.
We must delete the operator id to allow the user to login to App2 again.
Has anyone in the Pega realm has encountered this issue.
***Edited by Moderator Kayla to update Content Type from Discussion to Question***