OneOps
Connectors

Connector health

Sync status states, the sync log, and what to do about common errors.

Once a connector is live, the connector-health view tells you whether it is working. This page covers the status states, the sync log, and common errors.

Sync status states

Each connector shows a status:

  • Active. Recent syncs succeeded; data is current.
  • Warning. Something needs attention but the connector is still working (for example, slower-than-usual responses).
  • Error. Syncs are failing and data is not current.
  • Paused. The schedule is intentionally stopped, so failed runs do not pile up.

You will also see these states summarized in the intelligence dashboards overview's connector-health panel, alongside when each source was last checked.

The sync log

The sync log is the per-connector history of runs. For each run it records when it started and finished, how many records it touched, any errors, and the retry history. Use it to bound when a problem began and to confirm a fix took hold.

Common errors and what to do

These are the usual causes when a connector turns warning or error. Most resolve once the underlying source recovers or a credential is refreshed.
  • Authentication failed. A credential expired or was revoked. Re-enter the credential to rotate it (see Connecting a source).
  • Rate limited. The source is throttling requests. The platform retries; if it persists, the source may be under load.
  • Mapping error. The source changed its shape and a field no longer maps. Review the mapping and re-run a small test sync.

When a single connector starts failing while others keep running, check its last successful run in the sync log to bound the gap, confirm the issue is the source and not the mapping with a small manual sync, and pause the schedule if the source is down so failed runs stop piling up. Re-enable once a manual sync succeeds.

Catching up after an outage

If a connector was down or added late, run a sync with an explicit window covering the gap rather than changing the regular cadence. The reconcile step updates or inserts rather than duplicating, so a catch-up does not create double records. Check the counts against the source before considering it done.

See also

Sync and schedules

Sync rules, running more than one rule per source, and how data is normalized into a common schema.

Security

The public compliance posture: how the platform is designed to handle protected data, isolate organizations, and keep access minimum-necessary and audited.