Can you share a minimal repro repo via jsfiddle or https://codesandbox.io/ ? That would help a lot to understand what you are trying to do and what you want to archive

Sure will add

@B33fb0n3 Hey, due to NDA can't share the code. But on my app I have a service route, where when I navigate for the first time i.e. (before catch is stored) the navigation is happening but my loading page spinner is showing a long time inspite of the page has all static content with use client. I only have loading.js on my home page route that i.e.

src -/app -/about -/page.jsx -/pricing -/page.jsx -/service -/page.jsx -/page.js -/layout.js -/loading.js

Attaching the network request SS. Please If could help

thanks for sharing. I understand, that you can't share any details from the code itself. Right now I am still not able to provide you the help, that you need, because I don't see any code. Please create a reproduction repo. DONT share details included inside your NDA. You can share: the file structure and replace text inside it

When loading starts, nextjs will look for the suspense boundary(this is created by loading.tsx), once this loading boundary is used up, it wont be hit again till the next reload. Meaning it wont show up for components or pages inside the layout (if the layout trigged the suspense boundary) or even parallel routes if im correct.

To make it show for them you either have to explicitly define a suspense boundary(for components for example) or put a loading.tsx (for pages inside a layout)

1) Loading starts for layout (/loading.tsx HIT)
2) Actual page route inside the layout starts loading (/page/loading.tsx HIT)

(This is what i can remember from my own experience, maybe a bit wrong)

Ohhh thank you for sharing!