Live environments and sign-ins
Fix a 401 on a live run
Open the failed step: run history shows the sign-in calls with every credential masked, which usually points at the cause.
In Manage environments…, choose Test: it signs each role in and says what went wrong.
Check the token URL and client ID, and that the client allows the grant you picked (password grant, client credentials or the login page).
Auth0 needs its
audienceas an extra token field, or it hands out a token only its own userinfo accepts; Entra may needresource.Some APIs need a header on every call, such as Supabase’s
apikey: add it under the environment’s headers.Check the role’s test account: password, two-factor secret, and that the account exists on that environment.
Still failing? Explain this failure on the step names the likely cause from your code.
Didn’t answer your question? Contact support.