M.

So maybe it's an error on the end of supabase.

Got it — thanks, that makes sense. The 401 issue is fixed now and the function sends the invite email, but after the invited user clicks the email link they still land on the landing page instead of completing /auth/callback. So at this point the send step works, but the invite acceptance/callback step is still broken. Would you expect the invite acceptance flow to come back as ?code only, or should I also handle token/hash formats in my callback route?

I’m not using local hosting for this path — the function is deployed on project zgrjrbcruusihvwbowbm. I think the “Listening on http://localhost:9999/” line is just the edge runtime boot log, because that’s all I see before the 401. Dashboard JWT toggle is already off, and I also redeployed with --no-verify-jwt. I’m now adding this to config.toml too: [functions.invite-tester] verify_jwt = false and redeploying again.