> For the complete documentation index, see [llms.txt](https://helpcenter.channable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.channable.com/manage-improve-product-data/creatives-create-and-edit-images/troubleshooting.md).

# Troubleshooting

Expand the error message you see, then follow the matching resolution below.

<details>

<summary>Where do I find, and how do I resolve errors?</summary>

After activating your template in Image Rules, open **Preview & export**.

Select **Edited image errors** to view current errors.

Select an error to see its cause and affected items.

</details>

<details>

<summary>Field does not exist</summary>

This issue occurs when a template references a non-existent **Project Field**. This can happen when a text object in Project A uses `sale_percentage`. If Project B has no `sale_percentage` field, the error "This field does not exist!" appears when you apply the template.

<figure><img src="/files/8b798e6a7e8dec4009afb431e38ea968b12a3d2e" alt=""><figcaption></figcaption></figure>

Solution: Make sure that all referenced project fields exist in the projects in which the template is used.

</details>

<details>

<summary>Field is not of type Image</summary>

This message appears when a field does not have the `Image` type. This applies to image objects in the template and the field where the edited image is stored.

One way to run into this issue is if you are using a field like `image_link` and you import this field as a type `Text` as the field to "Store URL in" of an Image Rule.

<figure><img src="/files/f35cb79a7ecc3039456c393ecf8bfac5afa0b1e9" alt=""><figcaption></figcaption></figure>

Another reason for this error would be to not have a field set in the "Store URL in" part of the rule or to reference a non-Image field here.

<figure><img src="/files/a92703e76bfbc1d73a5368d0947d95482a79fdec" alt=""><figcaption></figcaption></figure>

Solution: Make sure that all fields used within the feature are of Type: `Image`. This can be done in the import mapping.

</details>

<details>

<summary>Image format is not supported</summary>

This error will be visible when anything other than PNG, WebP, JPG, or JPEG is used as an image format in the import. We can only process images of these formats as input. Note that the resulting images from the Image Editor will always be in PNG format.

</details>

<details>

<summary>Template does not exist</summary>

This happens when a template that has been deleted is (still) being referenced in a project. Since Templates can be accessed and deleted from anywhere in a company, there may be references to the deleted templates after they have been deleted. Rather than deleting every **image rule** in which the deleted template is referenced, a warning will be displayed where these templates are used.

<figure><img src="/files/1c957a8aad1ce95a108489f971cde17c3f64609b" alt=""><figcaption></figcaption></figure>

Solution: In each affected image rule, select a replacement template or remove the deleted template.

</details>

<details>

<summary>Image not tracked</summary>

#### What does this error mean?

This error means our system cannot locate the image URL you are trying to use.

Our system couldn't extract the image link from your import data. Even though your field may be set to "Image," the export failed for this specific item because the URL couldn't be processed.

#### How to solve this error

1. **Check your field type**\
   Ensure the project field has the `Image` type, not `Text`. You can still use an Image-type field as text in rules. Check this in **Setup** → **\[your import]** → **Mapping**.

   <figure><img src="/files/BmZ5PO6yuftrACF4bvcU" alt=""><figcaption></figcaption></figure>
2. **Only make URL changes in Setup > Import rules**\
   If you are using rules to change, clean up, or change your image URLs, make sure these rules are set up as [import rules](/manage-improve-product-data/rules-bulk-edit-and-enrich/rules-in-channable/import-rules-in-channable.md). This ensures our downloader reads the final URL and tracks it successfully. Changing URLs in channel rules means the downloader has already run, and it will miss the updated link.
3. **Verify your subscription/plan**\
   Image downloading is automatically included if you have the [Creatives plan](/account-billing/manage-your-subscription/channables-pricing-plans.md#creatives).

* **If you are not on the Creatives Plan:** You can still test the Image Editor, but images will only download if you are actively using an image template in an image rule.

</details>

<details>

<summary>Image not downloaded</summary>

This error will pop up when an image from an item in the stream that is being edited has not yet been downloaded. Because of that, we cannot generate the edited image.

After an image link has been extracted from the import, this link will enter a queue to have its image downloaded. This means that there is a delay between the import finishing and the images being available to generate edited images.

Solution: Wait until the image is downloaded. If the image never gets downloaded, check from the source (import) if the image is available for downloading.

</details>

<details>

<summary>Specific item is failing, but not sure which one</summary>

An export with Image Rules is failing because of a specific item. The error itself does not give a lot more detail. However, the most likely reason for this error is that the Unique ID for an item is not set.

Make sure that the correct (and the same) Unique ID is set for the project and the export. This should be a unique identifier per item that should be exported in the feed.

In the project settings, you can find the Unique ID here:

<figure><img src="/files/009eea197aee01c6d67d2ca06d06cfaf9f2e17de" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Note: The Unique ID in every export feed can have a different name. Example names for this unique number are `id`, `g:id`, `sku_id`, etc.
{% endhint %}

</details>

<details>

<summary>Image cannot be generated</summary>

Manage image-generation failures through [Safety settings](broken://spaces/UAGSVlvcNsqEqVUgr0tD/pages/a582eb7f77d6d196d45e334c4b7a8d8430bd0a01).

Go to **Settings** → **Advanced settings** → **Image generation safety**.

Choose one of these options:

* **Fail the feed and send a notification** — Stops the feed. This is the default.
* **Remove items where image generation fails** — Excludes only affected items.
* **Select project field containing backup image link** — Uses a fallback image from a project field.

</details>

<details>

<summary>Why are there no project fields shown? I want to select an image from my project fields.</summary>

No available project field has the `Image` type.

Create a project field or change an existing field to `Image` in **Setup** → **\[your import]** → **Mapping**.

</details>

<details>

<summary>Why do I get the message that there are no items?</summary>

Only one Image Rule can be applied to an item. The first Image Rule that includes an item will be the one applied to that item, and following rules selecting the item will skip that specific item.

Therefore, the order of the rules is important. We advise having the most narrow filters in the first rule, and then widen the filter for subsequent rules.

</details>

<details>

<summary>Why can’t I select a nested field as my result field?</summary>

This is due to technical reasons. We only support storing the edited images in non-nested fields, and therefore do not display nested fields in the dropdown for storing the URL.

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helpcenter.channable.com/manage-improve-product-data/creatives-create-and-edit-images/troubleshooting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.