# Cache Flushing Issue: Understanding WP Local and WP Engine Communication for Push/Pull

**URL:** <https://community.localwp.com/t/cache-flushing-issue-understanding-wp-local-and-wp-engine-communication-for-push-pull/43235>\
**Category:** Support\
**Tags:** windows-10\
**Created:** [June 7, 2024, 9:44pm UTC](https://community.localwp.com/t/cache-flushing-issue-understanding-wp-local-and-wp-engine-communication-for-push-pull/43235 "2024-06-07T21:44:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mkoduru](https://avatars.discourse-cdn.com/v4/letter/m/8491ac/32.png) [@Mkoduru](https://community.localwp.com/u/Mkoduru)\
**Post date:** [June 7, 2024, 9:44pm UTC](https://community.localwp.com/t/cache-flushing-issue-understanding-wp-local-and-wp-engine-communication-for-push-pull/43235/1 "2024-06-07T21:44:01Z")

</div>

Hello WP Local Community,

I’m currently facing an issue with my WordPress deployment workflow and could use some help understanding the process better. Here’s the situation:

I am using a local development environment (WP Local by wp engine) to manage my WordPress site. When I push my changes from WP Local to WP Engine, the database changes are immediately reflected on the WP Engine server URL. But when I use my git hub actions then the changes only appear after I manually clear the cache on WP Engine. This problem also occurs when deploying changes via GitHub Actions.  
My Questions:

1. How does WP Local communicate with WP Engine to push and pull changes?
2. What are the steps involved in the deployment process when pushing from WP Local to WP Engine internally?
3. Why might the database changes not reflect immediately, and how does cache flushing affect this?

---

<div class="post-metadata">

**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:** [June 8, 2024, 2:10pm UTC](https://community.localwp.com/t/cache-flushing-issue-understanding-wp-local-and-wp-engine-communication-for-push-pull/43235/2 "2024-06-08T14:10:03Z")

</div>

Hi @Mkoduru

With Local Connect + WPE our push includes a request that attempts to purge all WPE caches automatically and allow changes to show up right away without much manual effort needed.

When working with Github there is an optional `CACHE_CLEAR` deploy option you can input. There are details about this in WP Engine’s support center document below. Is that something you’ve tried already?

> **[GitHub Action for WP Engine Site Deployments - Support Center](https://wpengine.com/support/github-action-deploy/#Environment_Variables_and_Secrets)**
>
> With this GitHub Action you can easily create an automated deployment process from GitHub to WP Engine using our SSH Gateway.

---

<div class="post-metadata">

**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:** [April 9, 2025, 4:32pm UTC](https://community.localwp.com/t/cache-flushing-issue-understanding-wp-local-and-wp-engine-communication-for-push-pull/43235/3 "2025-04-09T16:32:45Z")

</div>

Closed on April 9, 2025, 4:32pm UTC

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
