#I encounted this when i visited my
terse sundial
check logs, also have you used error boundary ?
https://nextjs.org/docs/app/building-your-application/routing/error-handling
kind pollen
check logs, also have you used error boundary ?
https://nextjs.org/docs/app/buil...
Okay i will. I doesn't occur frequently though so i don't actually know how to re-create the error. I haven't used error boundary either. I will. Thank you
terse sundial
it might be an unhandled fetch denial, or something like that. usually programming an application takes also one to consider, exception handling, and displaying to client. High tech apps usually displays something like.. ops... something went wrong.. an error.. its not you but us..