Issue: Auth token refresh returning 500

[msholehhudin]

Issue: Auth token refresh returning 500 with error:
"missing destination name oauth_client_id in *models.Session"

Steps already taken:

• Restarted project via Settings > General
• Cleared auth.sessions and auth.refresh_tokens tables
• Issue persists after 1+ hour

This started after project was paused (free tier inactivity)
and then resumed. Refresh token endpoint consistently returns
500 for all users.

Here is the exact error message :

{
"code": "unexpected_failure",
"message": "missing destination name oauth_client_id in *models.Session"
}

from this endpoint :

auth/v1/token?grant_type=refresh_token

[bimalchokshi68-max]

request the reactivation of my Supabase project under the Free Plan.

[msholehhudin]

where i found it? but actually the project is running. while the problem is coming when token exipred. it cant refresh token after that

[hosanxiv]

This exact error points to an Auth service/database schema version mismatch, rather than invalid refresh-token data:

missing destination name oauth_client_id in *models.Session

Supabase Auth added oauth_client_id to auth.sessions in a migration, and the matching Auth release added an OAuthClientID field to models.Session. The error means the database query returned that column but the running Auth binary did not have a matching field, which is consistent with the database schema being newer than the Auth instance serving this project.

Official source:

• oauth_client_id session migration
• Matching field in the current Session model
• Original Auth change introducing both pieces

Deleting rows from auth.sessions or auth.refresh_tokens cannot repair this mismatch, and I would not drop or rename the column manually. On a hosted project, this needs Supabase to reconcile or redeploy the Auth service for the project.

Please open a support ticket and include the project ref privately, the UTC time the project was resumed, the complete error, and that every request to /auth/v1/token?grant_type=refresh_token is affected. Specifically ask them to check whether the project is running an Auth image older than its applied Auth migrations.

Because the session tables were cleared, affected users will need to sign in again after the service is repaired.

[msholehhudin]

i have opened a new support ticket and explain about my trouble but since this is free tier plan, they would not prioritize it as an urgency problem. they mention it on the email. overall thanks for explaining.

[erickdronski]

This exact error has appeared before in #40036, including for projects immediately after they were unpaused.

missing destination name oauth_client_id in *models.Session is a server-side Auth/schema compatibility error. It is not a missing field in your refresh request, and changing the client SDK or clearing cookies will not repair it. Deleting rows from auth.sessions and auth.refresh_tokens also does not repair the underlying mismatch.

For a hosted project, I would try this in order:

1. Open Project Settings → Infrastructure and apply any available infrastructure upgrade. This is different from simply clicking “Restart project.” Multiple users in Bug Report: missing destination name oauth_client_id in *models.Session during token refresh #40036 reported that the infrastructure upgrade fixed this exact post-unpause error.
2. Restart once after the upgrade, sign in again, and verify that POST /auth/v1/token?grant_type=refresh_token returns 200.
3. Avoid manually adding or dropping columns or continuing to delete data in the auth schema. Supabase Auth owns that schema, and manual modifications can interfere with future Auth migrations.
4. If no infrastructure upgrade is available, or the error remains, this needs Supabase Support. Include the project ref, unpause timestamp, Auth log timestamp, exact error, and a link to Bug Report: missing destination name oauth_client_id in *models.Session during token refresh #40036 so they can check the deployed Auth service and migration state.

The important distinction here is that a project restart restarts the current services, while an infrastructure upgrade can bring the service/database combination back onto compatible versions.