Skip to main content
ConnectorSyncDiagnostic is an infrastructure-layer audit log that captures structured failure and informational signals emitted by SyncConfigService during MCP connector sync execution. Each row records the exact tool invoked, the target entity model being synced, the reason the sync event was notable (a failure class or an informational signal such as jury telemetry or pipeline degradation), and a free-text detail message. Rows are tenant-scoped to a Workspace and linked to the specific WorkspaceConnector that triggered the sync. Retention is opportunistic: ConnectorSyncDiagnosticService.write() prunes rows older than 30 days for the current connector on approximately 1-in-20 writes — no separate scheduled job is needed.
Internal object. Not currently exposed on the public REST API. The operations below describe the intended contract.

API operations

Data model

Attributes

Relationships

System-computed

  • diagnostic_id — generated by gen_random_uuid() at DB level; never supplied by the caller
  • occurred_at — set to now() by MikroORM onCreate hook at insert time
  • created_at — set to now() by MikroORM onCreate hook at insert time
  • updated_at — set to now() by MikroORM onCreate and onUpdate hooks
  • deleted_at — set by application-level soft-delete; also used as the threshold for opportunistic hard-delete pruning (rows older than 30 days for the current connector are pruned inside ConnectorSyncDiagnosticService.write() on approximately 1-in-20 writes)
  • pk (internal) — serial auto-increment; not exposed via the public API

Example

Source: apps/api/src/database/entities/ConnectorSyncDiagnostic.ts · domain: ingestion · tier: Infrastructure