Unsure how to trace this production error.
Unanswered
English Springer Spaniel posted this in #help-forum
English Springer SpanielOP
Every so often I keep seeing this error in production:
I'm not sure how I trace this error or where to even start to fix this error. Is anyone able to help?
Thanks ahead of time!
Error: Couldn't find all resumable slots by key/index during replaying. The tree doesn't match so React will fallback to client rendering.I'm not sure how I trace this error or where to even start to fix this error. Is anyone able to help?
Thanks ahead of time!
9 Replies
Have you made a custom SSR setups with React ?
English Springer SpanielOP
I'm not sure what your question is here @RxvxntxN , I haven't not for this setup. I'm using cache components via "use cache" and cacheTag.
Mugger Crocodile
@English Springer Spaniel Where is this hosted?
English Springer SpanielOP
On vercel. Sorry, lol, I think I was tired and forgot to provide that information.
Mugger Crocodile
can you provide the hosted link ? or something
@Mugger Crocodile can you provide the hosted link ? or something
English Springer SpanielOP
I wish I could, the project is private for now. What information would I need to further debug this?
Also again, thank you for the help here!
Also again, thank you for the help here!
Mugger Crocodile
There are a lot of possible reasons for it. main reson is something in hydration mismatch Server vs Client HTML difference
@English Springer Spaniel I'm not sure what your question is here <@161854740165033984> , I haven't not for this setup. I'm using cache components via "use cache" and cacheTag.
That info doesn't help us to identify your issue. You can try
reactStrictMode that might help you identify the issue or try npm build in your project.Since your project is private , you have to show specific code that causing problem. Else, it is hard for us to help you.