# Caching errors **URL:** \ **Category:** Support\ **Tags:** mac\ **Created:** [January 31, 2024, 2:02pm UTC](https://community.localwp.com/t/caching-errors/41117 "2024-01-31T14:02:43Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Jerry](https://avatars.discourse-cdn.com/v4/letter/j/5daacb/32.png) [@Jerry](https://community.localwp.com/u/Jerry)\ **Post date:** [January 31, 2024, 2:02pm UTC](https://community.localwp.com/t/caching-errors/41117/1 "2024-01-31T14:02:43Z")
### What issue or error are you experiencing? After pushing from Local to WPEngine, the new code/style changes do not display on the dev; the code has been pushed–it can be seen in the theme files–but if I Inspect thru the console, the code is not shown; this happened so often on this new build, that we deleted the original environment, and started again, now it’s happening again with this new instance * * * ### What steps can be taken to replicate the issue? Feel free to include screenshots, videos, etc I deleted the original environment as WPEngine said they could not replicate the issue; the new instance was fine until two days ago; I pushed from Local and got an error "\*\*We ran into an issue when purging the CDN and page caches. … \*\* Since then, we’ve been experiencing the same issue, days after the changes were pushed; clearing caches, histories, changing machines and networks and browsers didn’t seem to matter; we have the same experience … sometimes the correct version displays, but refresh or clear the cache and the old version displays, or vice versa ![Screen Shot 2024-01-30 at 5.02.51 PM](https://us1.discourse-cdn.com/flex019/uploads/lwpforums/original/3X/1/5/15e6bc2fb90e50e8fe63b32ef5c82d39b0471139.png) the first screenshot above is the correct version, below that, the incorrect one; this is just one example; any page that was updated after I got that CDN error message, seems to flip back and forth between the old and new (from changes pushed more than 24 hours ago, and after clearing caches and histories) ![Screen Shot 2024-01-31 at 8.34.20 AM](https://us1.discourse-cdn.com/flex019/uploads/lwpforums/original/3X/7/1/71e88c3d1a99f1137ab0b51d3b390ecb083d3d7d.jpeg) ![Screen Shot 2024-01-31 at 8.34.04 AM](https://us1.discourse-cdn.com/flex019/uploads/lwpforums/original/3X/b/1/b172b01d9a6349473394230eff87dc39071fa2c8.jpeg) Here’s another page in incognito; that is the old version: ![Screen Shot 2024-01-31 at 9.24.44 AM](https://us1.discourse-cdn.com/flex019/uploads/lwpforums/original/3X/6/8/68deed023ebac560ad50fc66eaf2baca0ae56b17.jpeg) here’s what the page should look like ![Screen Shot 2024-01-31 at 9.27.17 AM](https://us1.discourse-cdn.com/flex019/uploads/lwpforums/original/3X/4/0/402726f5444cd4ec9bbf029e223b2006963e5626.jpeg) * * * ### System Details - **Local Version:** first time was on 8.1+. after first issue, updated to 8.2.1 - **Operating System (OS) and OS version:** Mac OS 12.2.1 * * * ### Local Logs Attach your Local Logs here ([Help Doc - Retrieving Local’s Log](https://localwp.com/help-docs/troubleshooting/retrieving-locals-log-file/)) ## [local-lightning.log](https://community.localwp.com/uploads/short-url/fjKYO0EnaIGgEpu5RVpAAAiUXrO.log) (978.2 KB) _ **Security Reminder** _ Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed. ---
**Author:** ![Nick-B](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nick-b/32/16140_2.png) [@Nick-B](https://community.localwp.com/u/Nick-B)\ **Post date:** [February 3, 2024, 2:54pm UTC](https://community.localwp.com/t/caching-errors/41117/2 "2024-02-03T14:54:10Z")
Hi @Jerry Is this just a recent error that started popping up around when you made this post? Or have you run into this problem in the past? There were some intermittent server issues on the WPE platform recently that errors in your log may point to being the issue. Are you still running this problem now? If you haven’t checked please test it again and let us know if the result is the same. If so then we may need to loop in WPE support to get a ticket up to their platform engineering team to look at the specific server. Keep us posted and we’d be happy to help further! ---
**Author:** ![Jerry](https://avatars.discourse-cdn.com/v4/letter/j/5daacb/32.png) [@Jerry](https://community.localwp.com/u/Jerry)\ **Post date:** [February 5, 2024, 1:40pm UTC](https://community.localwp.com/t/caching-errors/41117/3 "2024-02-05T13:40:57Z")
Hi, About 3-4 weeks ago was when it first started; it was such an issue we destroyed that environment and started again. We were OK for a couple weeks, and then it started again (but only when that Local caching error was displayed) … However, since last Thursday, it seems to be OK, all the code and pushes are now displaying thanks ---
**Author:** ![sambrockway](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/sambrockway/32/18726_2.png) [@sambrockway](https://community.localwp.com/u/sambrockway)\ **Post date:** [February 5, 2024, 1:44pm UTC](https://community.localwp.com/t/caching-errors/41117/4 "2024-02-05T13:44:58Z")
Hi @Jerry - Thank you for the update. Glad to hear it’s working now, but if you run into more issues in the future please don’t hesitate to reach out. I’ll mark this thread as resolved, Sam ---
**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/system/32/1_2.png) [@system](https://community.localwp.com/u/system)\ **Post date:** [February 7, 2024, 1:45am UTC](https://community.localwp.com/t/caching-errors/41117/5 "2024-02-07T01:45:23Z")
This topic was automatically closed 36 hours after the last reply. New replies are no longer allowed.