Troubleshooting
When sync looks off, start here.
Delayed refreshes, stale stock, missing fields, and duplicate records usually leave a pattern worth checking before blaming the queue.
Common sync patterns
Pattern
What to do
Sales moved but stock did not
Check whether stock updates arrive on a different schedule than sales.
Whole fields are blank
Check connector scope, field mapping, and whether the source system exposes the field on the current plan.
Products appear twice
Check duplicate records and catalog normalization before trusting the queue.
The queue looks stale
Check the last successful refresh before assuming the ranking itself is wrong.
Checks
- 1
Read the freshness state
Know whether the data is fresh, delayed, failed, or missing a field.
- 2
Check the source system
Confirm the source actually changed when the team expected it to change.
- 3
Check the mapping
A field can exist and still land in the wrong place if normalization is off.
- 4
Check the effect on recommendations
A sync issue matters most when it weakens a real decision path.
When to wait and when not to
Some sync delays are harmless if the review is tomorrow. Others break the whole point of the queue. The difference is whether the missing update changes a decision the team is about to make. If it does, the product should say so plainly.