Preserve the exact diagnostic before changing creative assets
A merchant sees an ingestion alert and concludes that every product photograph is unusable. Replacing the whole catalog can create more uncertainty while leaving the actual failing row unchanged. Record the source version, ingestion time, diagnostic code, scope and affected product IDs before deciding which file or image needs repair.
Pinterest documents code111 as a row-level failure for a missing image_link URL: affected items are not published. Code155 is a row warning when supporting-image values exceed ten; some images are omitted. Code2 is a file-level warning that ingestion ended early because the source did not change. These conditions require different actions. Do not generalize a single row message into proof that the complete catalog failed.
Use scope to choose the repair
| Recorded diagnostic | Repair target | What to avoid |
|---|---|---|
| 111 on one product | That product's exported main-image value | Regenerating every catalog photograph |
| 155 on one product | That row's selected supporting-image list | Assuming the item itself was necessarily rejected |
| 2 for the source | Whether a real source update was made | Calling unchanged input a new image-quality failure |
| Another code or file error | Its actual documented failure and scope | Applying one of these three fixes without evidence |
Walk one fictional repair through the export
Suppose BAG-BLUE has a valid source photograph in the merchant's asset library, but its exported image_link cell is blank. A screenshot of the library does not establish that the feed contains the URL. Inspect the exported row, confirm the correct authorized image and repair the field through the normal data-source owner. Recheck that exact row in the next authorized ingestion.
A separate BAG-GREEN row contains twelve supporting views. Select the justified ten or fewer rather than randomly deleting two URLs. Keep views that answer distinct buyer questions and match the green variant. These are proposed repairs to invented records, not an actual ingestion result. A valid URL and row count also do not establish image acceptance, public placement or conversion.
Reconcile after the update
Keep a before-and-after record of the source version, affected IDs, edited fields, next ingestion and remaining diagnostics. If the old error persists, confirm the platform read the intended revised source before making another creative change. For hosted feeds and manual uploads, the update path differs; see the catalog update workflow.
Check observed public products separately from ingestion status. A product can remain absent for another eligibility issue, and a previous Pin can remain visible while a new source is under review. Use product-group and board scope to avoid mistaking organization for successful row publication.
Close the right issue
Resolve the diagnostic only when the corrected source was actually processed and the affected condition is no longer reported or has a documented next owner. Do not report an image-generation improvement when the repair was an empty feed field. CartVisual does not read your Pinterest account or submit these updates automatically.