Is it safe to ignore occasional next-auth CLIENT_FETCH_ERROR reports if everything seems fine?
I'm running t3 app with ~100 users on vercel using Next-auth, and I'm getting these errors in sentry. I'm fairly certain these are happening because of network issues on the client that I really don't have any control over, but I'm not sure how to ensure that's the case? Is there a way I can configure next-auth to handle these more gracefully?
Error message:
[next-auth][error][CLIENT_FETCH_ERROR]
https://next-auth.js.org/errors#client_fetch_error Failed to fetch [object Object]
Errors | NextAuth.js
This is a list of errors output from NextAuth.js.
0 Replies