Catalog scan progress and recovery
Interpret catalog evidence, choose resume or a fresh scan, and recover interrupted reviews.
A Tally catalog scan prepares review rows from a particular company, master discovery, and product policy. Scanning does not approve product writes or publish Shopify products.
Before starting
- Confirm the selected company and an online, compatible Agent.
- Refresh masters after changing the Tally catalog.
- Review field ownership and creation defaults.
- Open Products → Tally → Shopify and select Scan Tally catalog.
Keep TallyPrime available during discovery. Avoid changing the source catalog or product policy while preparing a scan whose results you intend to approve.
Read progress correctly
| Evidence or stage | What it establishes | What to do |
|---|---|---|
| Discovery | The Agent is collecting source masters | Keep the selected company available |
| Materialization | The cloud is preparing durable source rows | Watch the progress timestamp before starting more work |
| Review-row creation | Source rows are being compared with mappings and policy | Review only rows that are ready |
| Lifecycle checks | Missing source relationships are being evaluated | Review archive behavior and blockers |
| Tally count matched | Independent count and identity/content checks passed | Continue reviewing destination changes |
| Connector snapshot checked | Internal snapshot checks passed without independent Tally count proof | Do not treat this as proof for automatic lifecycle changes |
| Completed | The scan finished its preparation stages | Review and approve eligible proposals |
A complete scan is evidence of preparation, not proof that every product is synchronized. Review rows can still require mapping, approval, or correction.
If progress stops
Check the last progress timestamp, scan status, recovery count, and Activity. Restore an offline Agent or unloaded company first. If the Agent is online and the cloud stages remain stalled, ask the operator to inspect the worker and queue.
Record the scan identifier and last progress time before starting recovery. Repeated recovery attempts are useful diagnostic evidence; a rising recovery count does not establish that a scan is healthy.
Resume or start fresh
| Situation | Recovery approach |
|---|---|
| Interrupted work, with the same company, discovery, and policy still intended | Use Resume when offered and when the scan remains eligible |
| Company changed | Bind and discover the intended company, then start fresh |
| Masters, mappings, defaults, or ownership changed | Refresh the source and prepare a fresh scan |
| Independent count or identity proof failed | Stabilize the source, refresh discovery, and inspect the failure before scanning again |
| Destination identity is ambiguous | Resolve the mapping or duplicate SKU before approving that row |
Cancellation takes effect at a safe batch boundary. Already staged rows remain; cancellation does not undo approved product writes. Inspect existing mappings and review outcomes before another approval.
After recovery
Confirm that progress advances, inspect failed or blocked review rows, and check whether any related inventory baselines need review. Use bounded bulk approval only after reviewing the selected proposals.
Scan history provides aggregate evidence. Its observed rows-per-minute rate is specific to that run and does not certify a supported catalog size or completion time. See Supported behavior.