Server-side cache bug preventing site_url update
Project ID: kvjnkicikdbkevwwaiyp
Issue: JWT state tokens contain cached old site_url despite correct configuration
VERIFIED EVIDENCE:
✅ Site URL set to: https://flowagent.sh/
✅ Redirect URLs include: https://flowagent.sh/ and https://flowagent.sh/**
✅ Frontend generates correct OAuth URLs with proper redirect_to parameter
✅ All local configs verified correct (frontend uses right Supabase project)
❌ OAuth flow redirects to: dev.d252tv2c7d0toe.amplifyapp.com (old cached URL)
This is the exact scenario described in your troubleshooting docs as requiring manual cache flush.
REQUEST: Please flush the config cache for project kvjnkicikdbkevwwaiyp
Decoded JWT state consistently shows:
"site_url": "https://dev.d252tv2c7d0toe.amplifyapp.com/"
"referrer": "https://dev.d252tv2c7d0toe.amplifyapp.com/"
Despite redirect_to parameter being: https://flowagent.sh/
flow-forge-ai-canvas
Lovable Generated Project
flow-forge-ai-canvas
Lovable Generated Project
1 Reply
There is no caching involved in Supabase auth.
There is a database REST API cache for DB table names. It has nothing to do with Auth, JWT's or siteURL. That cache you clear your self in the SQL editor, but it is not your issue. You probably need to provide more info about where you are seeing these URL's and why you mean by JWT. Note this is a user helping user site and not monitored by Supabase. There are no known bugs with the siteURL process.
There is a database REST API cache for DB table names. It has nothing to do with Auth, JWT's or siteURL. That cache you clear your self in the SQL editor, but it is not your issue. You probably need to provide more info about where you are seeing these URL's and why you mean by JWT. Note this is a user helping user site and not monitored by Supabase. There are no known bugs with the siteURL process.