@kapa.ai I have a connection that I am trying to set up for the first time. Testing both the source and destination are successful. However, the connection is running endlessly - can you help me understand what is going wrong? I am looking at the logs and suspect there is a hidden failure or error but not sure how to parse the logs.

A connection running endlessly (hanging) is a known issue in Airbyte. Here's how to understand what might be happening and how to diagnose it: Why a Sync Might Hang Indefinitely Airbyte uses a heartbeating mechanism to detect unresponsive sources or destinations. If neither the source nor destination sends a "heartbeat" within a configured time frame, Airbyte triggers a heartbeat error and restarts the job. [Heartbeats] Common known causes include: 1. API sources with slow/asynchronous responses (e.g., Salesforce, Facebook, Amplitude) — no workaround currently exists. 2. Rate limiting — the source is being rate-limited for longer than the configured threshold. 3. Slow database queries — often caused by using an un-indexed column as a cursor in incremental sync, or an under-provisioned database. 4. Destination write slowness — typically due to insufficient destination resources relative to data volume. [Heartbeats] How to Parse the Logs When reviewing logs for a hanging sync, look for: • The last log line before the hang — this often indicates where the process is stuck (e.g., buffering, preparing tables, waiting for a response). • Network errors — messages like

java.net.SocketException: No route to host

can indicate connectivity issues between Airbyte and your source/destination. [MSSQL CDC hang] • Source/destination check results — look for lines like

SOURCE CHECK: Failed

or

DESTINATION CHECK: Skipped

, which indicate the connection check itself is failing silently. [Hanging sync jobs] • Configuration errors shown in red in the UI — if present, Airbyte recommends re-testing and saving the source or destination before retrying. [Connection status] Recommended Next Steps 1. Check the sync logs for the last meaningful log line — it will tell you which stage (source read, buffering, destination write) the job is stuck on. 2. Verify network connectivity from your Airbyte instance to both the source and destination. 3. Check for rate limiting — the Airbyte UI will display an informational message and countdown if the source is rate-limited. [Connection status] 4. Check resource availability — CPU, memory, and disk on your Airbyte host and destination. 5. If you can share the specific log lines where the sync appears to stop progressing, that would help narrow down the root cause significantly. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.

The last log line is "2026-03-31 141103 platform INFO Pipeline completed for workload: 0ed564cb-f431-4ec6-b67a-7d8b0451c26c_33_0_sync." @kapa.ai

New message text here

For the record - cpu was throttled at 100% so assuming it is that. Thank you @kapa.ai!

Glad you found the root cause! CPU throttling at 100% is a well-documented cause of stuck/hanging syncs in Airbyte. When the deployment is under-provisioned, you may notice jobs that remain in-progress for long periods with eventual failures related to unavailable pods. [Scaling Airbyte] To address this, you can: 1. Increase connector resource limits in your `values.yaml`:

global:
  jobs:
    resources:
      limits:
        cpu: "4"
        memory: "8Gi"
      requests:
        cpu: "2"
        memory: "4Gi"

Or via environment variables:

JOB_MAIN_CONTAINER_CPU_LIMIT

and

JOB_MAIN_CONTAINER_CPU_REQUEST

. [Resource limits] 2. Limit concurrent syncs to reduce CPU pressure:

worker:
  maxSyncWorkers: 5
  maxCheckWorkers: 5

[Scaling Airbyte] 3. Scale up your nodes or add more worker replicas if you need to run many syncs concurrently. Good luck with your setup! 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.