Fix “Catalog version stale” on Meta Commerce Manager
Meta hasn't received a feed update in longer than the schedule expected. Could be that the scheduled fetch failed, the feed file is unreachable, or someone disabled the data source.
What you see in Meta Commerce Manager:
Catalog version stale Stale catalog flags when Meta hasn't received a feed update in over 72 hours. The scheduled fetch may have failed silently; the source URL may be unreachable; the data source may have been disabled.
Audit Data Sources fetch history first. Failed fetches surface there with reason codes. Most stale-feed issues are configuration drift — the schedule disabled, the URL changed, the auth expired.
Top causes
- 1
Hosted feed URL became unreachable (CDN expiry, auth changes)
- 2
Scheduled fetch was disabled or failed silently
- 3
Source system stopped generating the feed
How to fix it
- 1
Check Data Sources page
Commerce Manager → Data Sources → your feed. Look at fetch history. Failed fetches show with reason codes.
- 2
Verify the hosted URL works
Open the feed URL directly. Confirm it loads, has data, and is properly formatted.
- 3
Re-enable scheduled fetches if disabled
Data Sources → Settings → confirm schedule is active.
- 4
Force a fetch
Manual fetch confirms the connection works end-to-end.
FAQ
What's Meta's tolerance for stale data?
Roughly 72 hours. Past that, items start being suppressed because data is considered too stale for accurate serving.
Last reviewed: 26 May 2026
Why wait? Start free.
See your products rewritten in 60 seconds. Add a card only when you go live.
- Start free, no card: import your catalogue and run the feed audit
- 10 free AI credits to see your product titles rewritten
- Go live with a 7-day free trial of Growth ($29/mo) or Pro ($49/mo)
- Pay-as-you-go AI credits after the free 10, from $5