@finlayconn it appears to have resolved itself. We’ve reached out to the team at Fastly to determine the root cause of this caching error. Your new post is up on the custom domain as well now and I’ll let you know as soon as I have more information. Thank you so much for your patience and understanding! 
1 Like