This sounds like it might be related to a problem we've been seeing with data caching in Next.js. You can check this thread to see if any of the solutions help:
We've also filed an issue on the Next.js GitHub, which you can see there. Feel free to upvote and subscribe to that issue.