CoodraDocs
Ask Coodra

Troubleshooting

Why the first queue may not be useful yet.

When the first review feels thin, noisy, or confusing, the usual problem is missing signal, weak context, or a connector gap.

Common symptoms

Symptom
What it often means
The queue feels too empty
The data feed is thin, key fields are missing, or the filters are too narrow to produce useful work.
The queue feels noisy
Weak data, duplicate products, or low-value candidates are outranking the work that matters.
Recommendations are hard to explain
The signal exists, but the product is not showing enough context to earn trust.
Important products are missing
The connector, catalog mapping, or freshness window may be dropping useful signal.

What to check first

  1. 1

    Field coverage

    Confirm the connector exposes the fields the recommendation type actually needs.

  2. 2

    Freshness

    Check whether the queue is working from recent sales and stock data or from the last successful refresh.

  3. 3

    Catalog quality

    Look for duplicate products, inactive items, or missing costs before blaming the ranking.

  4. 4

    Review scope

    Make sure the team is looking at the right store, role, or workflow for the first pass.

What usually fixes it

The first queue gets better when the missing context becomes visible. Sometimes that means finishing connector verification. Sometimes it means fixing a handful of product records. Sometimes it means tightening the queue so the team sees the ten items worth reviewing, not the 80 that technically matched a rule.

Next

Sync issuesStatus and errors