Replies: 1 comment
-
|
is that chatGPT? 😭🙏 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
I have a route handler that calls
revalidateTagwhen it receives requests. When I first deploy, it works every single time. I can hit the endpoint repeatedly and the cache clears like it should. But after the app runs for a day or so, it starts failing randomly. Maybe 2 out of 5 requests will actually clear the cache, the rest just serve stale data. Nothing changed in my code, same tag strings, everything identical.The weird part is if I rebuild and redeploy, it works perfectly again for a while, then degrades over time.
Things I've checked
Is there a way to debug this or see logs for what
revalidateTagis actually doing? Would help figure out if it's even seeing the tags or if something's corrupted internally.Also, is this a known issue with long-running production builds? Restarting the process fixes it which makes me think something's getting out of sync in memory.
Additional information
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions