2
Proper Error Propagation for Triggers on auth.users Table
Source: supabase/supabase#28296 · opened by @TheCodeDestroyer
Hey Supabase team! 👋
I’m using Supabase with an OAuth provider in my NextJS app, and I ran into an issue with error handling.
When a trigger function on the auth.users table raises an exception, the error doesn’t make its way back to the /api/auth/callback endpoint.
Right now the query param error_description just says Database error saving new user and the error_code is 500,
which makes it really hard to handle edge case flows if I have some custom logic around user creation.
I’m using Supabase with an OAuth provider in my NextJS app, and I ran into an issue with error handling.
When a trigger function on the auth.users table raises an exception, the error doesn’t make its way back to the /api/auth/callback endpoint.
Right now the query param error_description just says Database error saving new user and the error_code is 500,
which makes it really hard to handle edge case flows if I have some custom logic around user creation.
No pledges yet. Be the first to back this.
Comments
Similar requests
Enhancement: Add API endpoint to query Auth user by email
3 votes · 0 comments
Cannot add "email" provider to an existing user
1 vote · 0 comments
Standardize Error Codes Across Supabase Ecosystem
1 vote · 0 comments
Better indication for webhooks (and link them!) in triggers view
2 votes · 0 comments
Enable table-based grouping/sorting for Database Management views
1 vote · 0 comments
No comments yet.