The job of this console
Scan cards, open a failure, fix mapping or data, retry, confirm the canonical row. Do not run dependent payroll or billing on a red pipe.
Integrations · Health
Sync Monitor
Last run, lag, and errors per connector — a monitor, not the place you map fields or edit Employee.
Scroll to Flowcharts. Scenario: Monitor integration sync health.
Health
Whether the pipe is actually flowing
Sync monitor shows last run, lag, and errors. It does not edit employees or projects. Red means fix the job, the map, or the source.
Integrations → Sync monitor
Route
/integrations/sync-health
Org flag syncHealthEnabled
Integration admin · Ops
Seat at the table
Integration admins and ops with syncHealthEnabled.
The working rhythm
Daily glance, drill red, retry or remap, verify in product.
Moments that bring you here
Morning ops. After a vendor outage. Before a payroll export. When Sales says POs did not land.
ⓘ
Monitor only
Admin scheduled jobs is platform cron. This page is connector health.
Flowcharts
1 — Red card then the failed job
See health, open the job or log, fix mapping or source.
flowchart TD
A[Open Sync monitor] --> B[Read cards]
B --> C[Failed job]
C --> D[Logs / mapping]
D --> E[Retry]
E --> F[Verify source entity]
- 1OpenIntegrations → Sync monitor.
- 2CardsLast run, errors, lag.
- 3DrillJob or log.
- 4FixMapping or canonical data.
Overview
Sync monitor is operational health. Jobs run batches. Logs hold detail. Mapping is the contract. Canonical entities remain the business truth when a payload is wrong.
How to use
1. Green before dependent work
Do not start payroll on a stale time export.
2. Retry vs remap
Poison payloads need mapping, not infinite retry.
3. Admin jobs
Platform cron is a different console.