Hey @egami HubSpot uses cloudflare as the CDN, I've found the cache times to be quite tempermental tbh.
I know with publishing pages it does attempt to flush the CDN cache and push the latest version out but this can really be down to cloudflares update rules. As a rule of thumb I generally tell clients to not advertise newly published articles until at least an hour after last publishing. Realistically it updates in about a minute 9 times out of 10 but better safe than sorry.
Regarding all of your questions, no is the answer to most. HubSpot is a fully managed system which uses shared servers for most customers, as such you're not going to get access to the servers or their settings. That means cache, TTL or even a refresh time for a cache is not going to be accessible to you.
Tom Mahon Technical Consultant | Solutions Engineer | Community Champion Baskey Digitial
This seems like a pretty remarkable issue to me? I found that I can use '?hsDebug=true&hsCacheBuster' to see the true, non-cached version, but remove that and it's back to the cached version. Generally speaking, when it comes to websites/emails, time is of the essense. I made my theme updates 2.5 hours ago and the old version is still displaying... So, we can't send a campaign until HubSpot clears their cloudflare cache, and we have no way of confidently planning around it?
Hey @egami HubSpot uses cloudflare as the CDN, I've found the cache times to be quite tempermental tbh.
I know with publishing pages it does attempt to flush the CDN cache and push the latest version out but this can really be down to cloudflares update rules. As a rule of thumb I generally tell clients to not advertise newly published articles until at least an hour after last publishing. Realistically it updates in about a minute 9 times out of 10 but better safe than sorry.
Regarding all of your questions, no is the answer to most. HubSpot is a fully managed system which uses shared servers for most customers, as such you're not going to get access to the servers or their settings. That means cache, TTL or even a refresh time for a cache is not going to be accessible to you.
Tom Mahon Technical Consultant | Solutions Engineer | Community Champion Baskey Digitial
Okay, I still can't access the CDN and cache settings.
I have some additional questions though these may be different than cache issues...
Can I save a draft of an article so that others can double check it before publishing?
Do paths of each publishing article include category name?
Can I set a different file name including version number and updated date each time I publish an article?
Is there any workaround to deal with the cache issue besides the one you suggested (Tell clients to not advertise newly published articles until at least an hour after last publishing)?