Flexify Flexify

Why do I see “Failed to update feed” or “feed_info_not_reachable”?

If Flexify shows “Failed to update feed” or feed_info_not_reachable, the app cannot access the public feed-info URL on your store. This is often caused by bot protection, redirects, rate limits, timeouts, or CDN / proxy settings blocking the request.

If you received an email saying “An error occurred while generating your product feeds” and the app shows this message:

Failed to update feed. The previous version of the feed is still available.
Error: feed_info_not_reachable

this usually means that Flexify could not access the feed-info URL on your store while trying to generate the latest version of your feed.

The good news is that the previous version of the feed is still available.

What does feed_info_not_reachable mean? #

Before generating the full feed, Flexify checks a small public feed-info URL on your store, usually under:

https://your-store.com/a/feed/v2/superfeed-info.xml

If that URL is blocked, redirected, rate-limited, timing out, or returning an error page, Flexify cannot confirm the feed settings and shows the feed_info_not_reachable error instead.

What can cause this error? #

This error usually means that the feed-info URL could not be reached correctly.

Common reasons include:

  • bot protection or anti-bot challenges
  • Cloudflare, DataDome, or another CDN, proxy, or security service blocking the request
  • redirects to a password page or challenge page
  • rate limiting
  • timeout issues
  • 403, 404, or 503 responses
  • an error page being returned instead of the expected feed-info response

What should I check? #

Please make sure the public feed-info path can be accessed without challenge or blocking.

In many cases, this means:

  • allowlisting the path /a/feed/v2/superfeed-info.xml
  • relaxing bot protection for feed-related URLs
  • making sure the URL is not redirected to a password page or challenge page
  • making sure a CDN, proxy, or security service is not rate-limiting or blocking requests
  • exposing a public feed-info URL that does not require JavaScript challenge clearance

Can Flexify change these settings for me? #

No. We do not have access to your Shopify backend or to any security, CDN, or bot protection tools enabled on your store.

Because of that, we cannot provide exact step-by-step instructions for your specific Cloudflare, DataDome, or other security setup.

Who should I contact? #

If your store uses Cloudflare, DataDome, a CDN, proxy, or another security service, the best next step is usually to contact:

  • your developer
  • your CDN or security provider
  • or the support team of the service that manages those rules

If no third-party security service is involved, Shopify Support may also be able to help review the setup.

Need help? #

If you contact our support team, please include:

  • the full error message
  • your store URL
  • the feed URL, if you know it
  • whether you use Cloudflare, DataDome, a CDN, or another bot protection service
  • a screenshot of the security rule, challenge page, or blocked request, if available

That will help us confirm more quickly whether the issue is likely caused by blocked access to the feed-info URL.