Changes not publishing in Sanity, preview shows correctly but live site not updating

Hello - not sure if this is the right forum but somehow changes that are made in sanity are not published, but are seen in preview. Any ideas? We have two different sanity versions, and this is one that has not been used for some time. Thanks

Hi 👋 Sorry to hear your changes are not coming through. When you say they are not published, are you referring to not being able to publish documents inside the Sanity Studio or rather not seeing the changes reflected on a web front-end, for example?
Also, is this in local development or in production? If it's in production, is the site successfully rebuilding after you publish your changes?

- hello, I am changing an element in the studio, see the text coming through in “Open Preview” . However, after having clicked “Publish”, I do not see the change on the website.

This may be because whereas the preview is real-time, the change to your production (live) site relies on a build process to complete.
The preview loads the updated data from the Sanity Content Lake (our APIs) when you open it from the studio. However, the live site may only fetch the data on build, which means a publish action either triggers a rebuild of the site (which usually takes a few minutes to complete) or does not trigger anything and relies on you or one of your developers triggering a rebuild yourself.

This depends on the website's implementation and not the Sanity Studio per se. Where are you hosting the site (e.g. Vercel or Netlify)?

This may be because whereas the preview is real-time, the change to your production (live) site relies on a build process to complete.
The preview loads the updated data from the Sanity Content Lake (our APIs) when you open it from the studio. However, the live site may only fetch the data on build, which means a publish action either triggers a rebuild of the site (which usually takes a few minutes to complete) or does not trigger anything and relies on you or one of your developers triggering a rebuild yourself.

This depends on the website's implementation and not the Sanity Studio per se. Where are you hosting the site (e.g. Vercel or Netlify)?

Thanks for the clarification. I am just a “content writer” so this is helpful. Do I understand correctly that I should raise this with our interal developers as Sanity studio works as it should (Open preview shows correctly). I don’t know where we are hosting the site unfortunately.

That's right, I'd recommend getting in touch with the devs to ask them to rebuild the site as you've updated its content. Alternatively, perhaps they could explain a way for you to trigger these rebuilds yourself [or do them automatically] depending on how they set things up. They should also feel free to reach out to us here in case they have questions 🙂

Thanks Peter!