I get your point but this is not a bug. But it’s a result of how caching and route revalidation work in Next.js (App Router) when using static or incremental rendering. But to solve this issue i would recommend you to put more code snippets to understand the problem.