Changes not updated on CDN after build + live deploy

I’m setting up the netlify CLI on circleCI, and getting builds to work okay, but having problems getting those changes propagated to the CDN. I’ve copied the logs below, and see my changes on Unique Deploy URL but not Live URL. I would expect the contents of these URLs to be the same. The line CDN requesting 0 files makes me think that the issue is with the diffing?

Deploy path:        /home/********/project/frontend/build
Configuration path: /home/********/project/netlify.toml
Deploying to live site URL...
- Hashing files...
✔ Finished hashing 19 files
- CDN diffing files...
✔ CDN requesting 0 files
- Uploading 0 files
✔ Finished uploading 0 assets
- Waiting for deploy to go live...
✔ Deploy is live!

Logs:              https://app.netlify.com/sites/elegant-babbage-7f3c6f/deploys/5e8d49b112687e12d7c550f9
Unique Deploy URL: https://5e8d49b112687e12d7c550f9--elegant-babbage-7f3c6f.netlify.com
Live URL:          https://elegant-babbage-7f3c6f.netlify.com

Did you use the search before posting?
Searched for cdn diff and cdn not updating, and didn’t find anything relevant

Hi, @geoff616, the logging from the Netlify CLI above does show the CLI hashed the files and that all 19 files have already been uploaded to Netlify. No new files we uploaded and the existing files already uploaded were linked to this new deploy as well.

That being said, live URL and the deploy URL should show the exact same content. If this is not the case, would you please send us the x-nf-request-id response header for a URL which is showing the incorrect version?

There more information about this header here:

If that header isn’t available for any reason, please send the information it replaces (or as many of these details as possible). Those details are:

  • the complete URL requested
  • the IP address for the system making the request
  • the IP address for the CDN node that responded
  • the day of the request
  • the time of the request
  • the timezone the time is in

Once we have a request to analyze (using that header or other details above to find it) we can see what version was sent and why.

If an error is occurring we’ll be happy to file an issue and offer workarounds if possible. If there isn’t an error, we’ll be able to explain what happened, why it happened, and offer solutions to change this behavior.

Thanks Luke. I’ve already decided not to use Netlify to host my site.

I’m confused by your response. Did you check the live URL and the deploy URL to confirm they are not the same? If so, you should be able to generate your own x-nf-request-id without my involvement. Here is an example from: https://elegant-babbage-7f3c6f.netlify.com x-nf-request-id: 70f19362-2cf9-48fc-a85e-c3f792d8ca79-1783906

The logs say that 0 files were uploaded, but the files are different. This would seem to indicate the issue is somewhere around where the CDN decided to request 0 files (i.e. diffing the hashes).

Best of luck.

Hi Geoff, thanks for the additional information! If we have any updates on this situation, we’ll post them here. :muscle: