Hi @r.cauquil,
Thank you for your reply!
I am following up on your previous Posts here.
After testing the Post-User-Registration Action extensively, I managed to reproduce the same issues.
In this situation, I will reach out to our Engineering teams to inform them about this bug and have them resolve the issue.
In the meantime, you could work around this issue by using the Management API with Actions and requesting the Get a User by ID endpoint and filtering for the family_name and given_name attributes. Then, you can proceed to use these attributes for your implementation in the Post-User-Registration Action script.
You can learn more in our FAQ on How can I use the Management API in Actions?.
Please let me know if you have any questions. I’d be happy to clarify.
Thank you.