It seems to always complete in exactly 20 seconds, which I assume is a timeout somewhere on your side.
Now here is the odd part… If I use the “Try It” function within the Auth0 Management page, it completes properly almost immediately. Any suggestions would be appreciated.
I don’t know if this is related, but I’m using the NuGet package Auth0.ManagementApi v7.0.1 to connect to the API.
Hi Dan, the URL provided in the code is hitting my (existing) endpoint. We’re using it to transfer users from our system to Auth0.
Sorry for the confusion!
Edit: To clarify, that endpoint returning a 404 means that no user with that email address has been found within our system (which is a good thing in this case, as it’s a new user attempting to create an account).
Hmm yes, I don’t think you would see a timeout if it was an invalid token, but it would depend how your API was set up to handle it.
It seems like this error is usually happening when the webtask is either waiting for a response for long enough to time out or when there is no callback. Are you sure your API is giving a response? Can you try some console logging to see what is happening before you report the 404
Is there anything else you can suggest? It works fine on my local machine, and the deployment (seems to) have everything set up correctly… But the GetUser returns a timeout no matter what.
My API is returning data near-instantly from the “try it” page, or from a browser, or via Postman; It’s only when it’s called from Auth0’s actual login flow that causes problems, and when I check my logs, my API (seems to) return successfully.
(For what it’s worth, I tried replacing the async/await with a promise chain, but to no avail)