@kapa.ai 2026-03-27 213119 replication-orchestrator INFO Creating status: homedelivery:db_storesearchinsight - RUNNING 2026-03-27 213119 replication-orchestrator INFO Stream status TRACE received of status: STARTED for stream homedelivery:db_trackpricechanges 2026-03-27 213119 replication-orchestrator INFO Sending update for homedelivery:db_trackpricechanges - null -> RUNNING 2026-03-27 213119 replication-orchestrator INFO Stream Status Update Received: homedelivery:db_trackpricechanges - RUNNING 2026-03-27 213119 replication-orchestrator INFO Creating status: homedelivery:db_trackpricechanges - RUNNING 2026-03-27 213119 destination INFO i.a.c.i.d.r.SerializedBufferingStrategy(lambda$getOrCreateBuffer$0):108 Starting a new buffer for stream db_globalsearchinsight (current state: 0 bytes in 0 buffers) 2026-03-27 213119 destination WARN o.a.h.u.NativeCodeLoader(<clinit>):60 Unable to load native-hadoop library for your platform... using builtin-java classes where applicable 2026-03-27 213120 destination INFO o.a.h.i.c.CodecPool(getCompressor):153 Got brand-new compressor [.snappy] 2026-03-27 213120 destination INFO i.a.c.i.d.r.SerializedBufferingStrategy(lambda$getOrCreateBuffer$0):108 Starting a new buffer for stream db_globalsearchinsight_available_service_store (current state: 209 bytes in 1 buffers) 2026-03-27 213120 destination INFO o.a.h.i.c.CodecPool(getCompressor):153 Got brand-new compressor [.snappy] 2026-03-27 213120 destination INFO i.a.c.i.d.r.SerializedBufferingStrategy(lambda$getOrCreateBuffer$0):108 Starting a new buffer for stream db_ordercommissionhistory (current state: 1 KB in 2 buffers) 2026-03-27 213120 destination INFO o.a.h.i.c.CodecPool(getCompressor):153 Got brand-new compressor [.snappy] 2026-03-27 213120 destination INFO i.a.c.i.d.r.SerializedBufferingStrategy(lambda$getOrCreateBuffer$0):108 Starting a new buffer for stream db_easebuzzpayment (current state: 2 KB in 3 buffers) 2026-03-27 213120 destination INFO o.a.h.i.c.CodecPool(getCompressor):153 Got brand-new compressor [.snappy] 2026-03-27 213120 destination INFO i.a.c.i.d.r.SerializedBufferingStrategy(lambda$getOrCreateBuffer$0):108 Starting a new buffer for stream db_storesearchinsight (current state: 6 KB in 4 buffers) 2026-03-27 213120 destination INFO o.a.h.i.c.CodecPool(getCompressor):153 Got brand-new compressor [.snappy] 2026-03-27 213120 destination INFO i.a.c.i.d.r.SerializedBufferingStrategy(lambda$getOrCreateBuffer$0):108 Starting a new buffer for stream db_globalsearchinsight_serviceable_store (current state: 15 KB in 5 buffers) 2026-03-27 213120 destination INFO o.a.h.i.c.CodecPool(getCompressor):153 Got brand-new compressor [.snappy] 2026-03-29 133117 replication-orchestrator ERROR Failed to obtain or add access token 2026-03-29 133127 replication-orchestrator ERROR Failed to obtain or add access token 2026-03-29 133137 replication-orchestrator ERROR Failed to obtain or add access token 2026-03-29 133147 replication-orchestrator ERROR Failed to obtain or add access token 2026-03-29 133157 replication-orchestrator ERROR Failed to obtain or add access token 2026-03-29 133207 replication-orchestrator ERROR Failed to obtain or add access token

The repeated

Failed to obtain or add access token

errors in your logs indicate that the replication-orchestrator is unable to authenticate internally — this is a platform-level authentication issue, not a source/destination connector issue. Based on a similar case reported in the knowledge sources [token error issue], this error (

Failed to obtain or add access token

) appears during long-running syncs and can cause the sync to ultimately fail. A related issue [deploy issue] points to a known root cause: the

airbyte-auth-secrets

Kubernetes secret not being properly created or managed. Specifically, one user noted: > "It seems that the main problem here is to have the secret airbyte-auth-secrets pre-created. [...] having the secret pre-created and managed externally, the secret was not being updated even though I have configured the role to do so." Recommended steps: 1. Check your Airbyte version — Several token-related issues were fixed in newer releases. Upgrading to the latest stable version is generally recommended [deploy issue]. 2. If you're on Kubernetes, verify that the

airbyte-auth-secrets

secret exists and is correctly populated with valid dataplane client credentials. Ensure it is not being externally managed in a way that prevents Airbyte from updating it. 3. Check the timing — Your logs show the sync started on

2026-03-27

but the token errors only appear on

2026-03-29

, roughly 2 days later. This suggests the sync ran for a long time before the token expired or became unreachable, which is consistent with the pattern seen in long-running syncs [token error issue]. The knowledge sources do not provide a definitive fix beyond the above. If the issue persists, consider reaching out via the Airbyte Community Slack or opening a support ticket if you're an Airbyte Cloud customer. 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.