Administration
Run synchronization and troubleshoot jobs
Configure an operation and use Sync Manager and Logs to verify its result.
How to do it
- Open Administration → Integrations. On smaller screens choose the section from the section selector. Connect an app first, then authorize it if OAuth is required.
- In Data Mapping choose the saved connection, name the operation and enter its method and relative API path. Use Request for an API call or Import for supported JSON record upserts. Map required fields and the external ID before saving.
- Open Sync Manager and choose Run / test. GET operations also support Preview response. Process queued jobs manually when needed; scheduled runs require background processing to be configured.
- Open Logs and filter by status. Queued means waiting; Processing means claimed by a worker; Succeeded confirms the operation completed; Retry means another attempt is scheduled; Review needs investigation.
- Before replaying a write, check whether the provider already accepted it. Correct credentials, mappings or provider errors, then use safe replay where available. A saved connection alone does not confirm successful synchronization.
Check your result
Verify the job result and the actual destination record using its external ID. Empty history means no jobs have been recorded; it is not a synchronization failure.
Good to know
Never paste tokens into request bodies, non-secret headers, logs or support messages. Use the encrypted connection credential fields.
Still need help?
Tell us your BU code and the step where you got stuck. Do not include passwords, BU PINs, tokens or recovery codes.
Contact SupaChrome support