Every sync job Bridge runs — whether triggered on a schedule, manually, or by a webhook — is recorded with counters, timing, and a per-record error log. Sync logs are the first place to go when a sync produces unexpected results or fails.
Viewing Sync Jobs
- Open Bridge and go to Sync Jobs.
- The list shows every job across all connections, with columns for connection, entity types, direction, status, and the counts for processed, created, updated, skipped, and errored records.
- Use the filters at the top to narrow by connection or by status (pending, running, completed, failed, cancelled).
- Click any job to open its detail view.
Job Detail View
The detail view shows:
- Status — pending, running, completed, failed, or cancelled
- Triggered by — manual, profile (scheduled), webhook, or retry
- Entity types — which entity types were included in this run
- Direction — inbound, outbound, or bidirectional
- Date range — if the job was scoped to a date range, it is shown here
- Counts — processed, created, updated, skipped, errored
- Started at / Completed at — timestamps for the run
- Errors tab — individual error records (see below)
- Changes tab — a record of every change made in this run, with before and after data
Viewing Per-Record Errors
Click the Errors tab on a sync job to see the records that failed. Each error shows:
- Entity type (company, ticket, contact, etc.)
- External ID of the record
- Error message
- The raw data received from the external system at the time of failure
Common error causes include field type mismatches, missing required fields in the mapped data, and external records that reference unmapped companies.
Re-Triggering a Failed Job
To retry a specific failed sync job:
- Open the job detail view.
- Click Retry. Bridge re-enqueues the job with
triggered_by = retry. - The new job appears in the Sync Jobs list. The original job record is unchanged so you retain the full history.
To retry individual failed records without rerunning the whole job, go to Error Recovery (accessible from the main Bridge navigation). Error Recovery aggregates failed records across all jobs and lets you retry, skip, or resolve them individually or in bulk.
Cancelling a Running Job
If a job is stuck in the running state or you need to stop it, open the job detail and click Cancel. The job status changes to cancelled. Records already processed are not rolled back.
Sync Profiles and Run History
Sync profiles maintain their own run history. Open a sync profile and go to the Runs tab to see every execution of that profile, including status and record counts. This view is useful for spotting whether a problem is isolated to one run or recurring across many.
FAQ
How long are sync logs kept? Sync job records and error records are retained indefinitely unless you delete them via the Bridge settings (Settings > Delete Sync Data clears the local copy of synced entity data, but not the job history itself).
A job shows as completed but no records were created — why? Check the Skipped count on the job. Records are skipped when they are unchanged since the last sync (no update needed), when they are filtered out by field mapping conditions, or when their parent company has not been mapped. Open the Errors tab to confirm there are no silent failures.
Can I see what changed in a specific record across multiple sync runs? The Changes tab on each job shows the before and after state for every record touched in that run. To trace a record's history across multiple runs, search for its external ID in the Changes tab across jobs.