# Supabase Auth: session_not_found
> Supabase returns session_not_found when the session behind a request no longer exists, after a sign-out or a deleted session. Clear it and sign in again.
Canonical: https://app369.com/fix/supabase-session-not-found/
Last updated: 2026-11-09
session_not_found is the Supabase Auth error code for a request whose session no longer exists. The user signed out, or the session entry was deleted, while the app still held its tokens.
**Short answer**
When this code comes back, clear the local session with signOut and scope local, then show the sign-in screen. Then find what ended the session: a global sign-out on another device, a session limit in the Auth settings, or an admin or script that deleted sessions.
Rather not fix it yourself? [**App Fix Ticket**](https://app369.com/fixed-price/flutter-firebase-bug-fix/) starts with a fixed-price diagnosis, then a fixed price for the fix before any fix work.
## **Why the session is gone, and the fix**
1. 01 ### **The user signed out somewhere else**
> “Session to which the API request relates no longer exists.” [**Supabase docs, Auth error codes (session_not_found)**](https://supabase.com/docs/guides/auth/debugging/error-codes) signOut ends every session for the user by default, so other tabs and devices get session_not_found at their next request. Use scope local when only this device should sign out.```
// Sign out on this device only
await supabase.auth.signOut({ scope: 'local' });
```
2. 02 ### **A session limit ended it** On Pro plans and up, time-boxed sessions, an inactivity timeout or single session per user in the Auth settings end sessions on the server, checked at the next refresh. Check those settings if users are signed out on a schedule.
3. 03 ### **An admin or script deleted the session**
> “This can occur if the user has signed out, or the session entry in the database was deleted in some other way.” [**Supabase docs, Auth error codes (session_not_found)**](https://supabase.com/docs/guides/auth/debugging/error-codes) Deleting rows from auth.sessions, or deleting the user, removes the session the app still holds. Sign the user out locally and let them sign in again.
4. 04 ### **The app keeps retrying with the old tokens** Also check: a server or middleware that reads an old auth cookie keeps failing. Clear the cookie on this code instead of retrying.
Checked against the vendor’s docs on November 9, 2026: [Supabase docs: Auth error codes](https://supabase.com/docs/guides/auth/debugging/error-codes); [Supabase docs: User sessions](https://supabase.com/docs/guides/auth/sessions); [Supabase reference: signOut (scope)](https://supabase.com/docs/reference/javascript/auth-signout).
## **Rather hand it over?**
Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.
- [from $450**App Fix Ticket**One reproducible bug in an existing mobile or web app, diagnosed and fixed.**See scope and start**](https://app369.com/fixed-price/flutter-firebase-bug-fix/)
- [from $450**AI-Built App Rescue**A Lovable, Bolt or Cursor app checked end to end in 3 days, then its worst problems fixed at a fixed price.****No issues worth fixing, no charge.**** If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.**See scope and start**](https://app369.com/fixed-price/ai-app-rescue/)
[**All 127 Fiverr reviews**](https://app369.com/reviews/)
Related: [**Supabase users logged out (refresh token)**](https://app369.com/fix/supabase-users-logged-out-refresh-token/) · [**Supabase Auth session missing**](https://app369.com/fix/supabase-auth-session-missing/) · [**Supabase session lost on refresh**](https://app369.com/fix/supabase-session-lost-on-refresh/) · [**Supabase Storage bucket not found**](https://app369.com/fix/supabase-storage-bucket-not-found/)
Questions
## **More on this error**
**Is it the same as Auth session missing? **+
No. Auth session missing means the client has no session stored; session_not_found means the server no longer has the session the client sent.
**Was the user account deleted? **+
Not necessarily. The session ended; the user can usually sign in again with the same account.
**Can you fix it for me? **+
If one bug is the whole problem, the App Fix Ticket covers it: a written diagnosis first, then the fix. If the app has more going on, the Launch Check is a written check of the whole app. Each issue found is rated critical, high, medium or low, with where it is and how it was confirmed. No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way. This applies to the first 10 Launch Checks bought after October 30, 2026.
A different error?
## **Describe it and get a written quote**
Send the error and what you were doing. You get a written scope, a fixed price and a timeline; Simon replies by email, usually within one business day.
[**Describe your problem **→](https://app369.com/contact/) [**All fixes**](https://app369.com/fix/)