Hi @rueben.tiow,
Yes, the user definitely has the name property in auth0 when created this way.
If this was not the case, could you please confirm if you creating the user with the Realtime Webtask logs extension already opened?
Yes, I open the Real-time Webtask Logs first and then run the request. In the following image, you can see I opened the logger at 12:39pm and I ran the request at 12:48pm:
When I do the same thing with the Actions Logs, I see this:
Alternatively, using the Test feature in the Auth0 Debugger shows that the Action script works correctly.
I tested my Action using the action tester before opening up this issue and it was working there. From my original post:
When I use the action tester, that request has all the user information specified and my action works perfectly if I receive all the provided data, but somehow I’m not getting all that information in reality.
This is what is confusing me. It seems like the management API and action are working independently, but when used together, it doesn’t work. I’ve deduced that some processing must be happening in-between the two that makes it so that not all the data gets to the action. I have no clue where that may be happening because I don’t have any other hooks set up. I do have a rule that adds some information to the token, but that shouldn’t affect this either.
Giles