UPDATE I have identified the issue is in the second Action, the UserId is not the Auth0 user id that the account is now linked to. Upon logging in the second time around, the user id is the Auth0 user account. Now I need to find a way to handle that. Was hoping to redirect the user back through …

I resolved this issue. Once I got to the bottom of the actual problem, I was able to find the resolution to switch the primary user calling the api.authentication.setPrimaryUser to the auth0 user rather than the Enterprise user. The second action then used the correct userid.

Api/v2/users/{user}/permissions call not completing only sometimes

Get Help

system Closed May 9, 2025, 6:13pm 5

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Migration Auth0 rules to actions: event.user.identities are not updated in one action flow Get Help configuration , application	2	20	November 13, 2024
Account linking through Actions Get Help actions	20	10903	November 22, 2023
How to link accounts from `ACTION` Get Help	2	3180	December 29, 2022
Account linking through actions [Critical issue] Get Help actions	10	3842	January 22, 2024
Action - User does not exist after account linking Get Help login-experience , login-prompt-new-experience	1	938	February 1, 2024

Api/v2/users/{user}/permissions call not completing only sometimes

Related topics