What to do when a connection or synchronization fails
SC separates access failure, rate limits, temporary unavailability, mapping and per-record errors so a failed operation never looks successful.
We will show this workflow with your store data.
Check connection state
NOT CONNECTED, ERROR and DISABLED require different actions; an error is not hidden behind a green status.
Open the run
History shows time, trigger, result, row counts and bounded provider diagnostics without secrets.
Retry safely
A retryable failure can use the existing job foundation; a permanent error needs corrected data or access.
Quick check
Check credentials
Renew the key or OAuth access in your organization’s connection without sending the secret to support.
Check scope and mapping
Provider permission and required mappings must be ready before retry.
Repeat one run
Reconcile statistics and verify idempotency created no duplicate.
Honest boundary
Exact actions depend on the provider contract. SC masks credentials and cannot repair a disabled external account without its owner.
Related resources
How to import products into SC CRM
SC CRM product import guide covering SKU identity, field mapping, preview, skipped rows, run statistics and repeat imports without duplicates.
Want the same in your store?
Leave a request — we will show SC CRM on your own tasks and agree on connecting your store.