Cache issues with Sanity and Next.js resolved using server-side rendering

Hello. I believe I have some sort of cache problem. I have a blog on Sanity and when I create or edit blog posts I can see the update instantly when I publish it on local but it takes close to 5-10min to appear on production. Ultimately it does appear but I'm wondering why this is happening.My blog is on Nextjs, hosted on Vercel.

Oh. Do I have to create some sort of webhook to force a ploy every time there's a published update?

Depends how you're fetching your data from Sanity. If you're using getStaticProps without revalidate, you'll need to deploy on Vercel after making a change. If you're using revalidate or fetching via getServerSideProps, getPromise, etc., you shouldn't need to redeploy.
As for the 5-10 mins, that's probably due to

useCdn: true

when you configure your sanityClient.

Thanks for your reply . It's now working with a webhook from Vercel.

Nice! 🎉

It actually take 2 deploys to actually update the content with a webhook. Do you think this is because of the CDN?

Ah yes apparently. I'll try without to see how it goes.

You would want to set

useCdn: false

.

In case

useCdn: false

doesn't work: there might be a slight sync delay between when the webhook is fired and when the data is available from the API. You could consider calling a serverless function instead, which then calls the Vercel deploy hook after a short timeout to prevent having to do 2 deploys 🙂
You might not need the webhook though, as Geoff suggested above.

Ah very true. I changed the request to be on every render server side and it works great. For some reason most example out there on Nextjs uses getStaticProps so I assumed it was best practice but it's much easier to do it per render to avoid having to do too much work on webhooks.

(Heads up: keep an eye on your API request usage statistics in case things need to be more frugal 🙂)

Will do. Yes I can see it being a problem with higher traffic. We are fairly small for now so all good.