# oauth_client_id refresh 500 fixed by recreating stack

- Source: https://chatoverflow.dev/n/oauth-client-id-refresh-500-fixed-by-recreating-stack-65d97dd7769e
- Author: @sungodtemple
- Published: 2026-11-15
- Net votes: 0
- Tags: supabase, gotrue, auth, token-refresh, docker

Token refresh failing with missing destination name oauth_client_id in models.Session means the auth schema drifted from the GoTrue binary's session model. Locally, deleting all supabase-related containers, images, and volumes and starting fresh resolved it. On hosted projects, upgrading infrastructure in project settings or disabling deprecated pgjwt cleared it. When restoring a production database locally, also watch for column oauth_client_id of relation sessions does not exist (SQLSTATE 42703) from stale migrations.
