If a catalog's import failed or no products came in, open its Activity tab: the run's status and warnings name the cause. The main causes are the feed's web address, the source blocking Renable, and a broken feed. Fix the cause and import again, or ask Aimée to fix it for you.
My Feed Import Failed
If an import failed or no products came in, the run on the catalog's Activity tab names the cause. The main causes are the feed's web address, the source blocking Renable, and a broken feed.
Updated November 6, 2026
Start on the Activity tab: read the run#
Open the catalog, go to its Activity tab and look at the most recent import:
- Its Status tells you how it finished.
- Expanding the run shows the log, the stage-by-stage record of where it broke.
- Below the imports, the warnings describe the problem and drill down to the products affected.
The health strip at the top of the catalog page shows the same status at a glance. For a full tour, see Imports, warnings, and tracing a value.
Cause 1: the feed's web address is wrong, expired, or private#
Nothing imports when Renable can't reach your product feed. The address may have a typo or be incomplete, the feed may have moved or expired (some platforms issue links that stop working after a while), or it may sit behind a login. The notice says which:
| The notice | What it means and what to do |
|---|---|
| "That address returned a web page, not a product feed." | Often the feed needs a sign-in, or the address isn't a direct link to the feed file. Get the direct link from your store platform or feed tool. |
| "This feed needs a username and password", or the saved ones were rejected | The server asked for a sign-in. See Connecting a password-protected feed. |
| "The feed's server refused the request (HTTP 403 Forbidden) without asking for a sign-in." | Usually not a password problem. Open the address in a private browser window. If it fails there, the address may have expired or been revoked, so get a fresh link. If it opens, the server is blocking Renable: see Cause 2. If the notice says the server refused even with your saved username and password, also ask your provider whether they grant access to this feed. If your provider says the feed does need a sign-in, you can add one. |
| "We couldn't connect to the feed's server: its address didn't resolve, or the server didn't accept the connection." | Check the domain for a typo. If it's right, the server may be down or moving. The import tries again automatically, so a short outage clears on its own. |
| "The feed's address can't be fetched: it names no host, or it points at a private, loopback or cloud-internal address." | The address only works inside your own network, such as one starting with localhost or an internal IP address. Use the feed's public web address. |
There are two quick tests:
- Paste the exact address into a private (incognito) browser window. If it doesn't return the feed there, Renable can't read it either.
- Use the download button on the feed's card on the Data sources tab (auxiliary feeds have one too). It fetches the feed as an import does, with the same User-Agent and saved sign-in, and saves what your provider sends. It uses the address in your settings, even an unpublished edit, so you can check a corrected address before publishing it.
To fix the address:
- On the catalog's Data sources tab, edit the product feed. A live preview shows the parsed products, or the error, before you save.
- Paste in the corrected address. For a private feed, use the full URL that includes its access token, the same one that works in a private browser window. If your store platform offers an official connection, such as a Meta or Google Merchant Center account link, that handles the sign-in for you. See Working with catalogs.
- Publish the catalog, then import again.
Cause 2: the source is blocking automated fetching#
If the address is right but the fetch still fails, your website, server or CDN may be treating Renable as an unwanted bot. The usual sign is the HTTP 403 notice above, while the same address opens fine in your browser.
The fix is to set a custom User-Agent on the catalog and have whoever manages your site allow it. My website or CDN is blocking Renable has the setting, where the allow rule lives in the common CDNs, and what to tell your IT department.
Cause 3: the feed came through truncated or malformed#
If your server times out mid-response or a proxy cuts the feed off, your existing products stay and the catalog shows an error. Everything picks up again when your source sends a complete feed on the next scheduled import.
A CSV or TSV file cut off at the end of a row is the exception. It looks like a shorter feed, so the products missing from it leave the catalog, and they come back with the next complete import.
If the catalog shows an import error just after your site had a problem, check whether the source had an outage. See Questions about catalogs.
The import stopped partway because rows couldn't be read#
If 100 rows in a row of your product feed can't be read, Renable stops reading there and the import fails (Errors on the Activity tab). The run's summary and a dashboard notification say where it stopped, for example "The import stopped at row 4,827 of your feed because 100 rows in a row (rows 4,728 to 4,827) couldn't be read."
- Products before those rows were imported and updated as usual.
- The rest of the feed wasn't imported, and no products were removed: products further down keep their last imported version, so your ads keep running on them.
- Row 1 is the first product, so in a spreadsheet with a header row, row 4,827 is on line 4,828.
A row can't be read when the feed file is broken at that point, or when one of your Rules fails on it. A row that's only missing a value, such as a price, doesn't count: it's skipped and reported as a warning that names the field.
Open the feed at those rows, or ask Aimée to look at one with you, fix the cause, and import again. The notification clears once an import reads the whole feed.
The run says the import stopped with an unexpected error#
If your dashboard says an import stopped with an unexpected error, or that some product updates could not be saved, the fault is usually on Renable's side rather than in your feed or its address. Your ads keep running on the products already imported.
- Stopped with an unexpected error: the run is a failed import (Errors) and isn't retried on its own. The next scheduled import runs as usual, or use Import now to bring your changes in sooner. The notification clears once an import completes.
- Some product updates could not be saved: saving retries by itself, so there's nothing to start by hand. The notification clears once the updates are saved.
If the notification stays across several imports, contact support and include its text. For a catalog connected through a Meta or Google account link, also check that the connection is still authorized, because a revoked or expired connection can show up this way.
The import was cancelled by the database three times#
This is on Renable's side, and nothing is wrong with your feed or its address. When the database interrupts an import, the run shows Retrying… on the Activity tab and Renable tries again by itself, with no alert.
After three cancelled attempts the same run ends as a failed import (Errors), so you and any Import fails monitor see it. Its summary reads "The import was cancelled by the database three times and will be tried again at the next scheduled import.", and your dashboard shows a matching notification.
Your ads keep running on the products already imported, though recent changes may not have come in yet. Renable tries again at the next scheduled import, sometimes sooner, and the notification clears once an import completes. If it keeps coming back across several scheduled imports, contact support and include its text.
The import worked, but characters look garbled#
If accented letters or currency symbols show up as odd symbols (é where you expected é), the feed's character set was
detected wrongly. Renable detects it automatically, and the Encoding setting overrides that:
- On the catalog's Data sources tab, edit the product feed.
- Expand Advanced and find Encoding, which is on Auto-detect by default.
- Switch it to the character set your feed uses and watch the preview. Common ones are ISO-8859-1 (Latin-1) and Windows-1252 for Western-European feeds, or UTF-8. If you're not sure, try them until the preview reads correctly.
- Publish the catalog, then import again.
Import again after you fix it#
Publish your fix, then use Import now in the health strip. If you have unpublished changes, Import now warns you and offers Publish & import, which does both. See Fixing your feed data with rules.
Then check the Activity tab: a healthy run reports its new and updated products, and any remaining warnings point at what still needs attention.
Or ask Aimée#
Try "my import failed, can you fix it?". She can check that an address really serves products, find your feed from your store's web address, set it and publish once you approve. She can also wait for the import, report the counts and warnings, and look into a specific warning. To start from scratch, see Let Aimée set up your feed.
FAQ#
The import finished but zero products came in. Is that the same problem?
Often, yes. Renable may have reached an address that returned nothing usable. The run's warnings on the Activity tab say whether the feed was unreachable, empty or unreadable.
My products disappeared after a failed import. Are they gone for good?
No. A truncated or broken fetch removes nothing. Products that left because a CSV or TSV file was cut off come back with the next complete import, and your edits to them are kept for 30 days.