Troubleshooting a Failed Product Sync (Cloudflare or Security Plugin Blocking)
What this means
If a product sync (especially a Full Sync) shows as Failed, and opening the card's error detail shows something starting with Invalid JSON: followed by what looks like your website's homepage code, it means our system requested your product data but received your website's normal HTML page back instead of the expected data. This almost always means something between us and your store - usually Cloudflare - intercepted or blocked the request before it reached WooCommerce.
A Full Sync pulls your entire product catalog at once, which means many more requests in a short window than a regular sync. That burst of activity is often what triggers a security rule that a normal sync doesn't.
Step 1: Quick self-test (no changes needed)
Visit the following URL in your browser, replacing yourstore.com with your store's domain:
https://yourstore.com/wp-json/
This is a public WordPress endpoint that requires no login. It should display raw JSON text (starts with something like {"name":"...","description":"...").
- If you see JSON text: your site's basic API routing works. Continue to Step 2 - the issue is likely specific to automated/bulk requests rather than all API traffic.
- If you see your normal website instead: go to Step 2, Permalinks below first, since this points to a more basic routing issue.
Step 2: Check WordPress permalinks
Go to WordPress Admin → Settings → Permalinks.
Confirm the setting is not "Plain." If it's set to "Plain," WooCommerce's API routes can't resolve, and WordPress falls back to serving your homepage for any API request - which produces exactly this error.
Any option other than "Plain" (for example, "Post name") is fine. If you need to change it, just select a different option and click Save Changes - this is a safe, reversible setting change.
Step 3: Check Cloudflare Bot Protection
If your site uses Cloudflare, it may be blocking our sync as automated traffic - even if the Step 1 test above passed, since a browser request looks very different from automated sync traffic.
In your Cloudflare dashboard, go to Security → Bots. If Bot Fight Mode or Super Bot Fight Mode is turned on, follow this guide to allowlist our sync traffic:
Step 4: Check Cloudflare Rate Limiting rules
Still in your Cloudflare dashboard, go to Security → WAF → Rate limiting rules.
A Full Sync makes many rapid, paginated requests to pull your entire catalog - very different from a single normal request. If you have a rate-limiting rule covering your API paths, add an exception, or raise the threshold, for:
/wp-json/wc/v3/*
Step 5: Check the Cloudflare Security Events log
In your Cloudflare dashboard, go to Security → Events.
Filter to the approximate time of the failed sync and look for anything Blocked or Challenged - ideally from a request whose user agent contains Trove. This confirms directly whether Cloudflare intervened, and which specific rule fired, which helps narrow down whether Step 3 or Step 4 is the fix needed.
Step 6: Check for a security plugin (if applicable)
If your site also runs a WordPress security plugin (Wordfence, Sucuri, iThemes Security, or similar) in addition to Cloudflare, check its firewall or activity log for the same time window. If you find a blocked request from a user agent containing Trove, add an allow rule for that request pattern on your WooCommerce API path.
After making a change
Once you've made an update above, let us know what you changed (or what you found in the logs) and we'll re-run the sync. If none of the above turns anything up, let us know that too - we'll take it from there.