> For the complete documentation index, see [llms.txt](https://docs.codegiganten.de/plugin-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/reading-the-product-feed-fails.md).

# Reading the product feed fails

All error types when reading the product feed with cause and measure, the automatic retry and how to check the feed address.

Errors occur when reading the product feed, or the setup wizard cannot be completed. Without product data, the search cannot deliver results. This page shows how to find and fix the cause.

It concerns the **pull** way: our search system retrieves the feed of your shop over the internet. With push, your shop sends the products itself, see [Push and live synchronisation](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/push-and-live-sync.md).

## How to check the feed address

The feed address must be reachable **publicly, without login and without a block**.

1. In Shopware, open the sales channel of type product comparison (Marketing, Product comparison). At the very bottom you find the "Export URL". In the plugin you find the same address in the "Sources" area as the feed address, with the button "Open feed in browser".
2. Open the address in a **private browser window** in which you are not logged in. This is exactly how our search system sees it.
3. Check the result:
   * A page with XML loads that contains many `<item>` entries: the feed is fine.
   * A login prompt, an error page or a maintenance page appears: then the cause is access protection or the shop.
   * The page loads very slowly or aborts: the feed takes too long, see the table below.
   * A page without products loads: the feed is empty.

The address is built like this: domain of the sales channel, then `/store-api/product-export/`, the access key of the sales channel and the file name of the feed.

## Help in the wizard and in the "Sources" area

If indexing fails, the plugin explains the cause in simple words. You see:

* the title of the error type and, if known, the "HTTP status",
* the "Feed address" with the link "Open feed in browser",
* a list "This can be the cause" and a list "This is what you can do",
* a note for staging and test systems,
* a link to the documentation and a button to support.

In the "Sources" area, the same help is collapsed behind "Show help" and "Hide help".

## Automatic retry

The plugin retries temporary errors up to **three times automatically**, after **30, 60 and 120 seconds**. A countdown shows the next attempt: "We will try again automatically in {seconds} seconds (attempt {n} of 3)." If our search system indicates a longer waiting time, for example with too many retrievals, the longer time applies, at most 15 minutes.

You have three options:

| Button                 | Effect                                                               |
| ---------------------- | -------------------------------------------------------------------- |
| "Try again now"        | Starts a new attempt immediately, without waiting for the countdown  |
| "Stop automatic retry" | Ends the automatic attempts. You can try again yourself at any time. |
| "Try again"            | Appears when no countdown is running and starts a new attempt        |

After three unsuccessful attempts the plugin no longer retries automatically. For errors that do not go away by waiting, the note "This error does not go away by waiting" appears. Then fix the cause first and try again yourself afterwards.

## All error types

| Error in the plugin                               | Cause                                                                                                                                             | Measure                                                                                                                                                                                                         | Retried automatically |
| ------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- |
| "The feed is protected by a login"                | Password protection or Basic Auth (htaccess), IP block or firewall, bot protection such as Cloudflare                                             | Open the address in a private window: it must be reachable without login. Exclude the feed address from the protection or allow the retrieval with the user agent `CogiInsightSearch-Feed/1.0`. Then try again. | no                    |
| "Access to the feed is denied"                    | Password protection, IP block, firewall or bot protection                                                                                         | Make the address publicly reachable and allow the retrieval for the user agent `CogiInsightSearch-Feed/1.0`. Then try again.                                                                                    | no                    |
| "The feed was not found at this address"          | Product export deleted or deactivated, access key changed, domain of the sales channel is wrong (for example after a move or a copy of the stage) | In Shopware under Marketing, Product comparison, check that the export still exists and is active. Open the address in the browser. If needed, create the feed again in the wizard.                             | no                    |
| "The shop is in maintenance mode"                 | Maintenance mode of the shop or sales channel is active                                                                                           | End maintenance mode or exclude the feed address from it                                                                                                                                                        | yes                   |
| "The shop had an error while generating the feed" | Error in the shop, or a very large catalogue aborts during generation                                                                             | Check the Shopware log (`var/log`), open the address in the browser. For large catalogues, set "Generate in the background" in the product export.                                                              | yes                   |
| "Too many retrievals in a short time"             | The feed was retrieved too often in a short time                                                                                                  | Wait briefly. It is retried automatically.                                                                                                                                                                      | yes                   |
| "The feed took too long"                          | Generation takes too long, or the shop is under load                                                                                              | Set "Generate in the background" and a suitable interval in the product export. Try again later.                                                                                                                | yes                   |
| "The domain of the feed is not reachable"         | The domain cannot be resolved, for example a local or internal staging domain, or it is misspelled                                                | Use a publicly reachable domain for the feed channel. Check the domain of the sales channel.                                                                                                                    | no                    |
| "The server refuses the connection"               | The web server is not reachable or not started, or a firewall blocks                                                                              | Check whether the shop is reachable from outside. Allow it in the firewall.                                                                                                                                     | yes                   |
| "The SSL certificate is not valid"                | Certificate expired, does not match the domain or is self-signed                                                                                  | Set up or renew a valid certificate, for example with Let's Encrypt. Then try again.                                                                                                                            | no                    |
| "The feed is not valid XML"                       | The response is an HTML page or truncated, or the template was changed                                                                            | Check the content in the browser. Create the feed again in the wizard so that the matching template is used.                                                                                                    | no                    |
| "The feed contains no products"                   | The sales channel has no products, products are not visible or active, or a filter in the product export (for example stock) excludes all         | Check sales channel, visibility and dynamic product group. Check the address in the browser.                                                                                                                    | no                    |
| "The feed could not be loaded"                    | Catch-all case if no more precise cause is known                                                                                                  | Open the address in the browser and try again. If the error remains, contact support.                                                                                                                           | yes                   |

{% hint style="info" %}
The plugin only shows a precise cause if our search system can report it. If you only ever see the general case "The feed could not be loaded", check the feed address yourself as described above.
{% endhint %}

## Typical causes in detail

### .htaccess and password protection

Password protection through `.htaccess` or Basic Auth also locks out our search system. This applies to the whole shop and to individual paths. Exclude the feed address from the protection (path `/store-api/product-export/`) or allow the retrieval.

### Stage with password protection

Staging environments are often protected by password, IP block or internal domain. Since our search system retrieves the feed over the internet, the feed address has to be publicly reachable without login. If that is not possible, use the mode **push** for the stage: then your shop sends the products itself. See [Push and live synchronisation](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/push-and-live-sync.md) and [Stage and Live](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/stage-and-live.md).

### Firewall and bot protection

Firewalls and bot protection services can block the retrieval. The retrieval comes with the user agent `CogiInsightSearch-Feed/1.0`. Allow it or exclude the feed address from the protection. Blocks by IP address can also affect the retrieval.

### Maintenance mode, certificate and domain

* Maintenance mode of the shop or the sales channel blocks the retrieval. The error disappears once the mode is ended.
* An expired or self-signed certificate leads to an error that does not go away by waiting.
* After a move or a copy of the stage, the domain of the sales channel may no longer be right. Check it in the sales channel or create the feed again in the wizard.

### The feed is not generated or too slowly

For large catalogues, set "Generate in the background" in the product export. Then a scheduled task of Shopware creates the file. This task has to run. Changes to the catalogue and the template appear only with the next export run. Wait for it and then re-import the product data in the "Sources" area with "Re-import product data".

## If nothing helps

Open the support dialog in the plugin dashboard or the button to support in the error help. State the error type, the HTTP status and the feed address. More under [Troubleshooting](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/troubleshooting.md).

## Further reading

{% content-ref url="/pages/kRomH0o5aBX5iDGMqpD3" %}
[Stage and live](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/stage-and-live.md)
{% endcontent-ref %}

{% content-ref url="/pages/kG1p17yKCiPZb4o3gw2S" %}
[Push and live synchronisation](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/push-and-live-sync.md)
{% endcontent-ref %}

{% content-ref url="/pages/cPKiMg6nNvV0NE0owXnG" %}
[Troubleshooting](https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/troubleshooting.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.codegiganten.de/plugin-documentation/en/apps/search-intelligent-and-ai-optimized/reading-the-product-feed-fails.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
