You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I optimized the caching of my Next.js site. Previously I only had very few cache tags (only 2 or 3 tags iirc) for all data, and I now have set more specific tags, where I have ~40 tags. This way I can run revalidateTag() for only exactly the data that has changed, so I don't slow down my whole site as soon as there's a single tiny change.
But now I cannot deploy my site anymore. It stalls at "Deploying outputs..." and then just does nothing until it times out after 20+ minutes.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Summary
Hey,
I optimized the caching of my Next.js site. Previously I only had very few cache tags (only 2 or 3 tags iirc) for all data, and I now have set more specific tags, where I have ~40 tags. This way I can run
revalidateTag()
for only exactly the data that has changed, so I don't slow down my whole site as soon as there's a single tiny change.But now I cannot deploy my site anymore. It stalls at "Deploying outputs..." and then just does nothing until it times out after 20+ minutes.
I found an issue that is reporting exactly the same: vercel/next.js#59022
Specifically, it's not about the amount of tags on a single cache item. But overall the amount on tags. Even if I only have 1 tag per cache item.
I can also see that when I change the tags back so I only have a few (less than 5) unique tags overall, the deployment works again.
What can I do to fix this?
Thanks
Example
No response
Steps to Reproduce
See vercel/next.js#59022
Beta Was this translation helpful? Give feedback.
All reactions