@kapa.ai Our syncs are failing, I couldn't get complete logs 2026-07-22 054452 platform INFO Retry State: RetryManager(completeFailureBackoffPolicy=BackoffPolicy(minInterval=PT10S, maxInterval=PT30M, base=3), partialFailureBackoffPolicy=null, successiveCompleteFailureLimit=5, successivePartialFailureLimit=1000, totalCompleteFailureLimit=10, totalPartialFailureLimit=20, successiveCompleteFailures=4, successivePartialFailures=0, totalCompleteFailures=4, totalPartialFailures=0) 2026-07-22 054452 platform WARN Backing off for: 4 minutes 30 seconds. 2026-07-22 061952 platform INFO Retry State: RetryManager(completeFailureBackoffPolicy=BackoffPolicy(minInterval=PT10S, maxInterval=PT30M, base=3), partialFailureBackoffPolicy=null, successiveCompleteFailureLimit=5, successivePartialFailureLimit=1000, totalCompleteFailureLimit=10, totalPartialFailureLimit=20, successiveCompleteFailures=5, successivePartialFailures=0, totalCompleteFailures=5, totalPartialFailures=0) Backoff before next attempt: 13 minutes 30 seconds 2026-07-22 061952 platform ERROR Failing job: 7404, reason: Job failed after too many retries for connection 0aa52568-5f92-4b06-b7f3-5540cfda2b86

Sync Job Failing After Too Many Retries Your logs show that the sync job exhausted all retry attempts with 5 successive complete failures (no data synchronized in any attempt), hitting the

successiveCompleteFailureLimit=5

. The job was then terminated with:

Failing job: 7404, reason: Job failed after too many retries for connection 0aa52568-5f92-4b06-b7f3-5540cfda2b86

The retry backoff progression visible in your logs matches the default behavior: [Sync Jobs] Why you can't see complete logs A common cause of missing logs in self-hosted deployments is MinIO storage running out of disk space. The default MinIO PVC is only 500MB, which fills up quickly with frequent syncs. When storage is full, logs cannot be written, and jobs may fail with platform errors. [Sync Jobs Hanging] Recommended steps 1. Check MinIO storage — If you're on a Kubernetes deployment, verify the MinIO PVC isn't full. You can free space by deleting old logs:/storage/airbyte-storage/job-logging/workspace /storage/airbyte-storage/workload/output 2. Increase MinIO storage — Set a larger volume in your `values.yaml`minio storage: volumeClaimValue: 2Gi 3. Reduce Temporal history retention to prevent storage from filling up againenv vars TEMPORAL_HISTORY_RETENTION_IN_DAYS: 7[Sync Jobs Hanging] 4. View logs via the UI — Navigate to the connection's Job History tab, click the three dots next to the failing sync, and select View logs or Download logs to get the full error details. [Browsing Logs] 5. Investigate the root cause — The retries are all complete failures (no data synced), which typically points to a connectivity issue with the source or destination. Check if your source/destination credentials or network access have changed. Adjusting retry limits (OSS only) If needed, you can tune retry behavior via environment variables: [Configuring Airbyte] •

SYNC_JOB_RETRIES_COMPLETE_FAILURES_MAX_SUCCESSIVE

— max successive complete failures before failing •

SYNC_JOB_RETRIES_COMPLETE_FAILURES_MAX_TOTAL

— max total complete failures before failing The most important next step is to get the full logs to identify the underlying error causing each attempt to fail with no data synced. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help., with interactive elements