How to solve Feed Configuration not updating issue?.

You changed a product’s price, edited a feed’s attributes, or fixed a title — but the feed still shows the old data. This is almost always a caching problem: either CTX Feed is serving cached product data, or a caching/CDN plugin is serving an old copy of the feed file. This guide walks through the fixes in order, so your feed always reflects your latest WooCommerce data.

First, understand the three layers

A product feed passes through three places where old data can get “stuck.” Fixing the issue means clearing the right one:

1. The feed file itself. CTX Feed only rewrites the file when the feed is generated. Editing a feed’s configuration does not change the file until you regenerate it.
2. CTX Feed’s product cache. To generate feeds faster, CTX Feed caches product data between runs. If you changed products after the cache was built, a new generation can still read the old cached values.
3. Your caching / CDN plugin. Page and CDN caches (WP Rocket, W3 Total Cache, LiteSpeed, SiteGround, Cloudflare, and so on) can hold on to a copy of the feed URL and serve that stale copy to the channel.

Work through them top to bottom.

Step 1 — Regenerate the feed

After any change to products or to the feed’s configuration, rebuild the file:

1. Go to CTX Feed → Manage Feeds.
2. On the feed’s row, click Regenerate (or open the ⋮ menu → Regenerate).
3. Wait for it to finish, then open the feed URL (⋮ → Preview, or the Open feed icon in the Feed URL column) and confirm the new data is there.

If the fresh file is correct, you are done — the earlier “old” data was simply the previous file. If it is still wrong, move to Step 2.

Step 2 — Clear CTX Feed’s product cache

If a regenerated feed keeps showing outdated product information, the plugin’s cached product data is stale:

1. On Manage Feeds, click Clear Cache in the header (you can also purge it from CTX Feed → System → Settings → Cache → Purge cache now).
   • This also refreshes the attribute picker in the feed editor, so a custom field or post meta you added recently appears under Custom Fields & Post Metas right away.
   • If your site runs a persistent object cache (Redis Object Cache, Memcached, Object Cache Pro), make sure you are on CTX Feed 8.0.25 or newer: earlier versions only cleared the database copy of the cache there, so the in-memory copy kept serving old data until it expired. On an older version, flush the object cache from that plugin’s own settings instead.
2. Regenerate the feed again.
3. Preview it to confirm the values are now current.

You can also shorten how long data is cached under Settings → Cache → Cache lifetime (1 hour up to 24 hours, or Never expire) if your catalog changes very frequently.

Step 3 — Exclude the feed URL from your caching / CDN plugin

If the file is correct when you preview it inside WordPress but a channel or a fresh browser tab still fetches an old version, a page-cache or CDN layer is caching the feed URL.

CTX Feed already registers its feed folder (/wp-content/uploads/woo-feed/) as a cache exception with the major caching plugins automatically — including WP Rocket, LiteSpeed Cache, SiteGround Optimizer, Cache Enabler, Breeze, WP Super Cache, WP Fastest Cache, WP-Optimize, Swift Performance, Speed Booster Pack, Comet Cache and Hyper Cache — and it sends a “do not cache” signal that other caching plugins such as W3 Total Cache can respect. In most setups you do not need to do anything.

If your host or CDN still caches the feed, add the feed URL (or the whole /uploads/woo-feed/ path) to that tool’s cache exclusion list manually:

• Caching plugins — add the feed path to the plugin’s “Never cache these URLs” / cache-exclusion setting, then clear the plugin’s cache.
• Cloudflare or another CDN — create a cache rule (or bypass) for the feed path, and purge the cached URL.
• After excluding it, clear the cache once and re-fetch the feed URL to confirm you get the fresh file.

Step 4 — Remember the channel’s own fetch schedule

Even with a perfectly fresh file, Google Merchant Center, Meta Commerce Manager, and other channels only re-read your feed URL on their schedule (often once a day). Updating the file does not instantly update the channel. To see changes sooner, trigger a manual fetch in the channel:

• Google Merchant Center — open the feed and use Fetch now.
• Meta Commerce Manager — open the data source and use its manual/refresh option.

Troubleshooting checklist

• Config edits are not in the feed → you saved the config but did not regenerate. Click Regenerate.
• Regenerated file still shows old prices → Clear Cache, then regenerate.
• Preview is correct but the live URL is old → a caching/CDN layer is serving a stale copy; exclude the feed path and purge that cache.
• Everything is fresh in WordPress but Google/Facebook show old data → wait for the channel’s next fetch or trigger a manual fetch.
• Auto-updates never run → that is a scheduling issue, not caching; see Fix auto feed update not working issue.

Related guides

• Manage Feeds
• Fix auto feed update not working issue
• How to solve the Processing 10% feed generation stuck error
• How to solve the missing product issue