-
SummaryI'm experiencing this weird behaviour what in my This is actually not all the time, but for only for pages that really dont exist. For example Maybe related to this: Also the Seems like Additional informationNo response ExampleNo response |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 12 replies
-
|
You are right, since notFound returns NEXT_NOT_FOUND error with 404 status continuously, which terminates rendering routed pages. It is why you need to re-request (refresh) the page in order to render the page from the link URL.
ref: https://nextjs.org/docs/app/api-reference/functions/not-found |
Beta Was this translation helpful? Give feedback.
-
|
There's a fix on the making for this: |
Beta Was this translation helpful? Give feedback.
-
|
I'm still seeing this issue but I haven't been able to pin down what's causing it. When I call If I wrap the children of the main layout (where I have error boundaries but they're not triggered, and there are no console errors apart from the 404. |
Beta Was this translation helpful? Give feedback.
There's a fix on the making for this: