Hey @hrishikesh
Are there any updates on this? One of my clients projects is not really working well because of that issue in Netlify. I don’t wish to migrate to Vercel but if that doesn’t get resolved soon I might have to.
Would be nice if you have any updates on timeline for fixing that.
No updates at the moment, @OFranke_limebit. In an optimistic scenario, we might be able to fix this in a release we’re planning in October, but it’s far from being considered official - it’s more in a PoC stage.
We’re not investigating issues individually until we ship the new Next.js Runtime, so the cause of this issue has never been investigated. I believe it has something to do with how the ISR responses get cached when used in a combination with RSC, but that’s as far as the investigation has gone. There’s no known solution or workaround for this right now.
Once the new Next.js Runtime is shipped, it would automatically fix several issues and then we can revisit the issues that still need some manual fixes.