A deployment does not refresh my content

[ndimatteo]

A deployment does not refresh my content

[SMccarrick]

Hey @ndimatteo

The deployment logs look like a typical build nothing out of the ordinary. My dataset is set to production and my project name is slugified like so example-name.

I've just refreshed my tokens and it still isn't working.

I get that this probably more of an issue with my setup so I'll close for now

Cheers for your help

[ndimatteo]

@ansmlc check out this answer here, this is likely a cache issue: #26 (comment)

[ndimatteo]

Hey @SMccarrick !

What does your Vercel project show for deployment logs? And are you using the same sanity dataset and project name between your studio and frontend?

Given the nature of how the deployment plugin works, it's agnostic to the actual Studio you set it up in, as it's simply redeploying the specified Vercel project.

So, if your Vercel project isn't properly hooked up to the sanity project and dataset that you published changes to you won't see any updates reflected when you trigger a deploy.

[NikkiJonesR]

@ndimatteo having the same issue as above. The deployment shows correctly in the Vercel Dashboard however the content is not updated. When I manually redeploy the sanity vercel deployment again through the dashboard it works.

Update: After further investigation I'm finding that if I make a published change, I have to reload the Sanity Studio before hitting the deploy button - then the updated content will show once deployed. Could this be a state issue?

[ndimatteo]

Hey there @NikkiJonesR ! Would you mind going into a bit more detail about what you're experiencing? I'm not sure I follow!

Just to reiterate a few things in case it helps:

1. The Vercel Deploy plugin is agnostic to the studio it's installed in. The plugin only triggers a build of the specified Vercel project. You'll need to make sure the project ID and dataset hooked up to your Vercel project matches with where you're editing.
2. You'll want to always make sure any changes in the associated Sanity project dataset is published before triggering a deployment manually from the "Deploy" tab.

Looking forward to hearing more 🤘

[NikkiJonesR]

Hi @ndimatteo, yep for sure. I can confirm that the config is setup correctly, and changes are published.

Here's the issue I'm experiencing:

1. Publish a change in the Studio
2. Trigger deploy
3. The content updates on the site as expected
4. Return to the Studio and publish another change
5. Trigger deploy
6. The content doesn’t update on the site
7. Return to the Studio and reload the page
8. Trigger deploy
9. The content updates on the site as expected

Hope this helps!

[ndimatteo]

Thanks @NikkiJonesR, do you know how the page in question is rendered? is it SSG or ISR by chance? There have been issues raised about ISR pages with Vercel and rebuilds, and I'm wondering if that's a factor here.

If the deploy is triggering every time, and you're seeing it rebuild in Vercel, I'm struggling to see how this plugin would have anything to do with the build itself, as that's all offloaded to Vercel and how your front-end is built.

Curious if there's any other insight into your specific setup that may shine some light on this!

[NikkiJonesR]

Hi @ndimatteo the page I was testing on is SSG - nothing fancy we're doing there. It could be a Vercel issue, but it seems peculiar to me that when I do a hard refresh on Sanity it deploys as expected.

[moonstripe]

@NikkiJonesR - Ditto on the hard refresh thing. Did you find anything out?

[ansmlc]

I'm using Hull and supposedly this plugin as well. Same thing is happening. Deploying alone doesn't update the content without doing reloads.

[Nateight8]

Observed the same thing as did @NikkiJonesR with swell.is on nextjs app. Newly published contents don't get refreshed unless I redeploy, any quick fix?

[ndimatteo]

@Nateight8 check #26 (comment)