Force Update Files in PublicCDN

%3CLINGO-SUB%20id%3D%22lingo-sub-109153%22%20slang%3D%22en-US%22%3EForce%20Update%20Files%20in%20PublicCDN%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-109153%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3CBR%20%2F%3EHow%20do%20we%20force%20update%20files%20(js)%20in%20publiccdn%3F%3C%2FP%3E%3CP%3EThis%20article%20said%20that%20we%20have%20to%20wait%2015%20minutes%20to%201%20hour%20to%20see%20the%20updated%20assets%3A%20%3CA%20href%3D%22https%3A%2F%2Fdev.office.com%2Fblogs%2Fgeneral-availability-of-office-365-cdn%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdev.office.com%2Fblogs%2Fgeneral-availability-of-office-365-cdn%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20I%20have%20waited%20for%20several%20hours%2C%20but%20it%20still%20loads%20the%20old%20one.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20any%20way%20to%20force%20refresh%20the%20publiccdn%3F%20or%20any%20workarounds%20to%20make%20it%20loads%20the%20new%20one%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eupdate%3A%3C%2FP%3E%3CP%3EMaybe%20this%20is%20because%20I%20update%20the%20files%20by%20replacing%20(delete%20and%20than%20reupload)%20the%20whole%20folder%20with%20the%20new%20one.%20It's%20programmatically%20replaced%20by%20a%20SharePoint%20add-ins.%3C%2FP%3E%3CP%3EThen%20somehow%20the%20publiccdn%20doesn't%20see%20that%20as%20an%20update%20to%20the%20file.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-110036%22%20slang%3D%22en-US%22%3ERe%3A%20Force%20Update%20Files%20in%20PublicCDN%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-110036%22%20slang%3D%22en-US%22%3E%3CP%3EI%20found%20out%20the%20issue%2C%20I%20had%20disabled%20the%20force%20checkout%20in%20the%20library%20feature%2C%20but%20the%20js%20files%20were%20created%20as%20a%20minor%20version%2C%20I%20just%20had%20to%20publish%20them%20to%20have%20them%20available%20in%2015%20min%20in%20the%20CDN.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-109221%22%20slang%3D%22en-US%22%3ERe%3A%20Force%20Update%20Files%20in%20PublicCDN%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-109221%22%20slang%3D%22en-US%22%3EHi%20Christian%2C%3CBR%20%2F%3EI%20found%20a%20workaround%20by%20updating%20the%20file%20directly%20in%20the%20browser.%3CBR%20%2F%3EIt%20works%20in%20my%20dev%20tenant.%3CBR%20%2F%3EI'm%20still%20testing%20it%20in%20the%20production%20site.%3CBR%20%2F%3E%3CBR%20%2F%3EMaybe%20it%20works%20as%20well%20in%20your%20environment.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-109218%22%20slang%3D%22en-US%22%3ERe%3A%20Force%20Update%20Files%20in%20PublicCDN%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-109218%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Ari%2C%20I'm%20facing%20the%20same%20issue%2C%20almost%20one%20day%20since%20I've%20updated%20the%20file%20and%20it's%20not%20updated%20in%20the%20CDN%20yet.%20Did%20you%20find%20out%20why%20was%20it%3F%20Removing%20a%20creating%20the%20file%20again%20did%20the%20trick%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-109176%22%20slang%3D%22en-US%22%3ERe%3A%20Force%20Update%20Files%20in%20PublicCDN%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-109176%22%20slang%3D%22en-US%22%3E%3CP%3EIt's%20some%20javascript%20files%20loaded%20in%20a%20SharePoint%20page.%3C%2FP%3E%3CP%3EI've%20cleared%20all%20the%20local%20cache%20and%20tried%20using%20another%20browser.%3C%2FP%3E%3CP%3EEveryone%20having%20the%20problem.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20added%20some%20information%20in%20the%20initial%20post%2C%20maybe%20it%20helps%20to%20describe%20the%20situation.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-109169%22%20slang%3D%22en-US%22%3ERe%3A%20Force%20Update%20Files%20in%20PublicCDN%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-109169%22%20slang%3D%22en-US%22%3EWhat%20exactly%20is%20still%20loading%20the%20old%20one%3F%3CBR%20%2F%3EIf%20that%20is%20a%20browser%2C%20have%20you%20cleared%20the%20browser%20cache%3F%20Have%20you%20tried%20using%20another%20browser%20to%20see%20the%20change%3F%3CBR%20%2F%3EAre%20you%20the%20only%20one%20having%20the%20problem%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2020243%22%20slang%3D%22fr-FR%22%3ERe%3A%20Force%20Update%20Files%20in%20PublicCDN%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2020243%22%20slang%3D%22fr-FR%22%3E%3CP%3EWell%20done.%3C%2FP%3E%3CP%3EThanks%20for%20the%20tip%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi,
How do we force update files (js) in publiccdn?

This article said that we have to wait 15 minutes to 1 hour to see the updated assets: https://dev.office.com/blogs/general-availability-of-office-365-cdn

 

However, I have waited for several hours, but it still loads the old one.

 

Is there any way to force refresh the publiccdn? or any workarounds to make it loads the new one?

 

update:

Maybe this is because I update the files by replacing (delete and than reupload) the whole folder with the new one. It's programmatically replaced by a SharePoint add-ins.

Then somehow the publiccdn doesn't see that as an update to the file.

 

Thanks

6 Replies
What exactly is still loading the old one?
If that is a browser, have you cleared the browser cache? Have you tried using another browser to see the change?
Are you the only one having the problem?

It's some javascript files loaded in a SharePoint page.

I've cleared all the local cache and tried using another browser.

Everyone having the problem.

 

I've added some information in the initial post, maybe it helps to describe the situation.

Hi Ari, I'm facing the same issue, almost one day since I've updated the file and it's not updated in the CDN yet. Did you find out why was it? Removing a creating the file again did the trick?

 

Thanks!

Hi Christian,
I found a workaround by updating the file directly in the browser.
It works in my dev tenant.
I'm still testing it in the production site.

Maybe it works as well in your environment.

I found out the issue, I had disabled the force checkout in the library feature, but the js files were created as a minor version, I just had to publish them to have them available in 15 min in the CDN.

Bien vu.

Merci pour le tuyau