Hello folks,

All of a sudden I'm getting the following error on client side when loading my routes.

No default component was found for a parallel route rendered on this page. Falling back to nearest NotFound boundary.

This causes the routes not being loaded. Instead, the nearest NotFound boundary is loaded.
Also, the error is random (sometimes it does not happen). It appears with high probability when loading any of my routes, with exception of those that use only server components.

The problem is: I'm not using this fucking parallel routes feature anywhere in my app !

I have no idea about what is causing it. I already discarded the following three hypothesis:

1) Upgrade from next v14.1.4 to v14.2.3: I reverted the upgrade and the problem remains.
2) Use of next-auth in middleware with Prisma ORM: I removed the middleware and the problem remains.
3) This prisma issue: https://github.com/vercel/next.js/issues/64792#issuecomment-2080533446: I applied the fix proposed in the issue discussion and the problem remains.

Any help is appreciated.

Thanks