Queue
The Icecat Enrichment Queue is the module's work list. It states why an item has not been enriched yet — as a status, not a guess. Icecat answers one product in one language per request; the queue turns that into paced work that stays interruptible and observable.
Queueing Items
| Way | Where | Urgency |
|---|---|---|
| Get Icecat Content | Item card, group Icecat | Immediate — the item is requested on the spot, in every active language |
| Queue for Icecat Content | Item list, group Icecat | Background — the selected items are worked off by the next runs |
| Automatic | Setup, Queue New Items Automatically | Continuous — new items and changed identifiers queue themselves |
Entries from the item card run before bulk orders (someone is waiting there); the automatic content refresh runs behind everything else. An item that is already waiting is never queued twice.
The Columns
| Column | Meaning |
|---|---|
| Status | Pending (waiting), Processing, Completed, Error |
| Next Run | From when the entry is picked up — the re-check after "no match" and the backoff after failures show up here too |
| Retry Count | How often processing failed; after the third time the entry waits for a manual reset |
| Error Message | Why the last attempt failed |
No match is not an error
If Icecat does not carry a product, the entry is rescheduled for a re-check (Recheck Items Without Match After (Days)) and the content row carries the status No Match with a reason. Only technical problems count as errors.
Actions
| Action | Effect |
|---|---|
| Process Now | Works off the due entries immediately, up to Max. Items per Run. If nothing happens, the message names the reason: queue empty, or everything is waiting out a delay. An inactive or unconfigured module is named with a navigable error |
| Reset Errors | Puts all failed entries back in line, after a confirmation with the count. Fix the cause first — a replaced token, for example — then reset |
The Background Run
Schedule Background Run on the setup card creates the hourly job queue entry. The entry is deliberately not created at installation but on click only — and only while the module is active with a complete account. Once it exists, its schedule stays untouched.
A run that finds the module switched off or no longer licensed ends silently — a job failing every hour would only fill the log. At the start of every run, aged content is additionally re-queued at the lowest priority according to Refresh Content After (Days).