https://linen.dev logo
Join Slack
Powered by
I have a simple stream made with the low code conn...
# replication-ask-ai
l
I have a simple stream made with the low code connection builder in the tester it works normally but when running the connection, it just keeps logging this and never calls the upstream api 2025-12-26 155732 destination INFO DefaultDispatcher-worker-2 i.a.c.l.s.CheckpointManager(flushReadyCheckpointMessages):148 No checkpoints to flush 2025-12-26 155832 destination INFO DefaultDispatcher-worker-2 i.a.c.l.s.CheckpointManager(flushReadyCheckpointMessages):148 No checkpoints to flush 2025-12-26 155932 destination INFO DefaultDispatcher-worker-2 i.a.c.l.s.CheckpointManager(flushReadyCheckpointMessages):148 No checkpoints to flush 2025-12-26 160032 destination INFO DefaultDispatcher-worker-3 i.a.c.l.s.CheckpointManager(flushReadyCheckpointMessages):148 No checkpoints to flush 2025-12-26 160132 destination INFO DefaultDispatcher-worker-2 i.a.c.l.s.CheckpointManager(flushReadyCheckpointMessages):148 No checkpoints to flush 2025-12-26 160232 destination INFO DefaultDispatcher-worker-2 i.a.c.l.s.CheckpointManager(flushReadyCheckpointMessages):148 No checkpoints to flush 2025-12-26 160332 destination INFO DefaultDispatcher-worker-2 i.a.c.l.s.CheckpointManager(flushReadyCheckpointMessages):148 No checkpoints to flush 2025-12-26 160432 destination INFO DefaultDispatcher-worker-2 i.a.c.l.s.CheckpointManager(flushReadyCheckpointMessages):148 No checkpoints to flush 2025-12-26 160532 destination INFO DefaultDispatcher-worker-2 i.a.c.l.s.CheckpointManager(flushReadyCheckpointMessages):148 No checkpoints to flush 2025-12-26 160632 destination INFO DefaultDispatcher-worker-2 i.a.c.l.s.CheckpointManager(flushReadyCheckpointMessages):148 No checkpoints to flush 2025-12-26 160732 destination INFO DefaultDispatcher-worker-2 i.a.c.l.s.CheckpointManager(flushReadyCheckpointMessages):148 No checkpoints to flush 2025-12-26 160832 destination INFO DefaultDispatcher-worker-2 i.a.c.l.s.CheckpointManager(flushReadyCheckpointMessages):148 No checkpoints to flush 2025-12-26 160932 destination INFO DefaultDispatcher-worker-2 i.a.c.l.s.CheckpointManager(flushReadyCheckpointMessages):148 No checkpoints to flush 2025-12-26 161032 destination INFO DefaultDispatcher-worker-2 i.a.c.l.s.CheckpointManager(flushReadyCheckpointMessages):148 No checkpoints to flush
k
I'm sorry, but there is no specific information in the provided knowledge sources that explains the exact root cause of why a low-code connector would hang with "No checkpoints to flush" messages while never calling the upstream API, especially when it works in the tester. However, the knowledge sources do highlight similar "hanging" behaviors and provide some context for troubleshooting: * Symptoms of Stalling: The log message 
No checkpoints to flush
is a standard informational message from the 
CheckpointManager
. In cases of large or long-running connections, users have reported syncs stalling or hanging for long periods with these exact repeating logs [[MongoDbSource corrupted cursor](https://github.com/airbytehq/airbyte/issues/62832); [HubSpot mid-sync failures](https://github.com/airbytehq/airbyte/issues/62467)]. * Potential Version Issues: A similar hanging issue with the MSSQL connector was resolved by upgrading the Airbyte version (specifically to 0.39.x in that historical case), suggesting that core platform updates can sometimes resolve execution stalls [[Mssql CDC connector hangs](https://discuss.airbyte.io/t/1323)]. * Resource Constraints: If you are running Airbyte in "low-resource mode," certain features may be limited or behave unexpectedly. It is generally recommended to allocate the [suggested resources](https://docs.airbyte.com/platform/using-airbyte/getting-started/oss-quickstart#suggested-resources) for stable performance [[Connector Builder Overview](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/overview#disabled-in-low-resource-mode)]. * Internal Buffering: Sometimes a sync appears hung because the destination is waiting for buffers to flush. If a stream contains very few records (or just one), logs might show the system waiting indefinitely for a flush that hasn't triggered yet [[Sync hangs forever BigQuery](https://github.com/airbytehq/airbyte/issues/58082)]. Since the tester works but the live sync does not, you might want to verify if there are any network or authentication differences between your local environment (where the tester runs) and the environment where the Airbyte worker is executing. If the issue persists, you may need to check the full logs for any 
SocketException
or 
Timeout
errors that might appear after a long delay [[Mssql CDC connector hangs](https://discuss.airbyte.io/t/1323); [S3 stalling](https://github.com/airbytehq/airbyte/issues/56926)].
l
@kapa.ai TaskWrapper(LoadPipelineStepTask(ObjectLoaderPartLoader, part=5)) 2025-12-26 184007 destination INFO DefaultDispatcher-worker-12 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(LoadPipelineStepTask(ObjectLoaderPartLoader, part=8)) 2025-12-26 184007 destination INFO DefaultDispatcher-worker-9 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(LoadPipelineStepTask(ObjectLoaderPartLoader, part=9)) 2025-12-26 184007 destination INFO DefaultDispatcher-worker-12 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(LoadPipelineStepTask(ObjectLoaderUploadCompleter, part=0)) 2025-12-26 184007 destination INFO DefaultDispatcher-worker-9 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(LoadPipelineStepTask(BulkLoaderTableLoader, part=0)) 2025-12-26 184007 destination INFO DefaultDispatcher-worker-7 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(LoadPipelineStepTask(ObjectLoaderPartLoader, part=7)) 2025-12-26 184007 destination INFO main i.a.c.l.t.DestinationTaskLauncher(run):173 Launching update batch task 2025-12-26 184007 destination INFO DefaultDispatcher-worker-2 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(LoadPipelineStepTask(ObjectLoaderPartLoader, part=6)) 2025-12-26 184007 destination INFO DefaultDispatcher-worker-2 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(io.airbyte.cdk.load.task.internal.UpdateBatchStateTask@24b3e358) 2025-12-26 184007 destination INFO main i.a.c.l.t.DestinationTaskLauncher(run):176 Launching heartbeat task 2025-12-26 184007 destination INFO DefaultDispatcher-worker-2 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(io.airbyte.cdk.load.task.internal.HeartbeatTask@6b491385) 2025-12-26 184007 destination INFO main i.a.c.l.t.DestinationTaskLauncher(run):185 Starting checkpoint update task 2025-12-26 184007 destination INFO DefaultDispatcher-worker-9 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(io.airbyte.cdk.load.task.internal.UpdateCheckpointsTask@7cb8652e) 2025-12-26 184007 destination INFO DefaultDispatcher-worker-9 i.a.c.l.t.i.UpdateCheckpointsTask(execute):34 Starting to consume checkpoint messages (state) for updating 2025-12-26 184008 destination INFO DefaultDispatcher-worker-5 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):36 Task TaskWrapper(io.airbyte.cdk.load.task.implementor.SetupTask@73475d0e) completed 2025-12-26 184107 destination INFO DefaultDispatcher-worker-5 i.a.c.l.s.CheckpointManager(flushReadyCheckpointMessages):148 No checkpoints to flush 2025-12-26 184207 destination INFO DefaultDispatcher-worker-2 i.a.c.l.s.CheckpointManager(flushReadyCheckpointMessages):148 No checkpoints to flush I think it might be hanging on the "checkpoint update task˜ I just copied the exact same stream with another name so it starts from stach it still doesnt work
k
A message from kapa.ai
I'm sorry, but the provided knowledge sources do not contain enough information to determine if the "checkpoint update task" is specifically causing your connection to hang or why a newly renamed stream would continue to exhibit this behavior. The knowledge sources do, however, provide some context regarding these log patterns: * Checkpoint Logs are Often Passive: The message 
No checkpoints to flush
is a standard heart-beat style log from the 
CheckpointManager
. While it appears frequently when a sync is stalled, it often indicates that the destination is waiting for data to process rather than the task itself being the cause of the hang [[S3 stalling on large connections](https://github.com/airbytehq/airbyte/issues/56926); [HubSpot mid-sync failures](https://github.com/airbytehq/airbyte/issues/62467)]. * Source vs. Destination Hangs: In similar reported issues, when the logs stop at checkpoint or buffer messages, the root cause was sometimes found to be a failure in the Source Check or a failure of the source to actually emit records. For instance, if the source check fails or hangs, the destination will continue to wait and log that there are no checkpoints to process [[All sync jobs hanging](https://github.com/airbytehq/airbyte/issues/55812)]. * Infrastructure Interferences: In one case involving Kubernetes (EKS), syncs hung indefinitely at the "finalization" or "checkpoint" stage because of an external sidecar container that wasn't being closed properly, preventing the worker from completing its lifecycle [[Redshift Destination Hanging](https://discuss.airbyte.io/t/4574)]. The knowledge sources do not explicitly mention why a low-code connector would work in the tester but fail during a live sync with these specific logs. I recommend checking the Source logs (not just the destination logs) to see if the HTTP requests are actually being dispatched by the worker, as the "No checkpoints to flush" message typically confirms the destination is healthy but idling.
l
@kapa.ai q 2025-12-26 184005 replication-orchestrator INFO Workload successfully transitioned to running state 2025-12-26 184005 destination WARN main c.k.j.j.JsonSchemaGenerator$MyJsonFormatVisitorWrapper(expectAnyFormat):725 Not able to generate jsonSchema-info for type: [simple type, class com.fasterxml.jackson.databind.JsonNode] - probably using custom serializer which does not override acceptJsonFormatVisitor 2025-12-26 184005 destination INFO main i.a.c.l.c.DataChannelBeanFactory(dataChannelMedium):60 Using data channel medium STDIO 2025-12-26 184005 destination INFO main i.a.c.l.c.DataChannelBeanFactory(namespaceMapper):308 Going to use the given source value: SOURCE for namespace 2025-12-26 184005 destination INFO main i.a.c.l.c.DestinationCatalog(<init>):49 Destination catalog initialized: [DestinationStream(unmappedNamespace=cacau_show_totvs, unmappedName=srd__acumulado, importType=Dedupe(primaryKey=[[RECNO]], cursor=[_synced_at]), schema=ObjectType(properties={CC=FieldType(type=StringType, nullable=true), CPF=FieldType(type=StringType, nullable=true), NOME=FieldType(type=StringType, nullable=true), HORAS=FieldType(type=StringType, nullable=true), RECNO=FieldType(type=StringType, nullable=true), VALOR=FieldType(type=StringType, nullable=true), VERBA=FieldType(type=StringType, nullable=true), DESCCC=FieldType(type=StringType, nullable=true), FILIAL=FieldType(type=StringType, nullable=true), FUNCAO=FieldType(type=StringType, nullable=true), EMPRESA=FieldType(type=StringType, nullable=true), PERIODO=FieldType(type=StringType, nullable=true), HISTFUNC=FieldType(type=StringType, nullable=true), DATA_PGTO=FieldType(type=StringType, nullable=true), MATRICULA=FieldType(type=StringType, nullable=true), TIPO_LANC=FieldType(type=StringType, nullable=true), DESC_VERBA=FieldType(type=StringType, nullable=true), TIPO_VERBA=FieldType(type=StringType, nullable=true), _synced_at=FieldType(type=StringType, nullable=true)}, additionalProperties=true, required=[]), generationId=0, minimumGenerationId=0, syncId=1370106, isFileBased=false, includeFiles=false, destinationObjectName=null, matchingKey=null, namespaceMapper=io.airbyte.cdk.load.command.NamespaceMapper@c04f2d2)] 2025-12-26 184006 destination INFO main i.a.c.l.c.DataChannelBeanFactory(logPerNRecords):137 Logging every 100000 records 2025-12-26 184006 destination INFO main i.a.c.l.f.s.S3ClientFactory(make):196 Creating S3 client using Kotlin SDK 2025-12-26 184006 destination INFO main i.a.c.l.c.DataChannelBeanFactory(dataChannelSocketPaths):69 Using socket paths [] 2025-12-26 184006 destination INFO main i.a.c.l.s.PipelineEventBookkeepingRouter(<init>):80 Creating bookkeeping router for 1 data channels 2025-12-26 184006 destination INFO main i.a.c.l.c.DataChannelBeanFactory(dataChannelFormat):79 Using data channel format JSONL 2025-12-26 184006 destination INFO main i.a.c.AirbyteConnectorRunnable(run):35 Executing class io.airbyte.cdk.load.write.WriteOperation operation. 2025-12-26 184006 destination INFO main i.a.c.l.t.DestinationTaskLauncher(run):158 Starting input consumer task 2025-12-26 184006 destination INFO main i.a.c.l.t.DestinationTaskLauncher(run):163 Starting startup task 2025-12-26 184006 destination INFO DefaultDispatcher-worker-1 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(io.airbyte.cdk.load.task.internal.InputConsumerTask@1216d8a4) 2025-12-26 184006 destination INFO DefaultDispatcher-worker-1 i.a.c.l.t.i.InputConsumerTask(execute):78 Starting consuming messages from the input flow 2025-12-26 184006 destination INFO main i.a.c.l.t.DestinationTaskLauncher(run):167 Launching open stream task 0 2025-12-26 184007 destination INFO main i.a.c.l.t.DestinationTaskLauncher(run):167 Launching open stream task 1 2025-12-26 184007 destination INFO DefaultDispatcher-worker-1 i.a.c.l.t.i.ReservingDeserializingInputFlow(collect):32 Reserved 296mb memory for input processing 2025-12-26 184007 destination INFO DefaultDispatcher-worker-3 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(io.airbyte.cdk.load.task.implementor.SetupTask@73475d0e) 2025-12-26 184007 destination INFO main i.a.c.l.t.DestinationTaskLauncher(run):167 Launching open stream task 2 2025-12-26 184007 destination INFO DefaultDispatcher-worker-6 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(io.airbyte.cdk.load.task.implementor.OpenStreamTask@4e321e58) 2025-12-26 184007 destination INFO DefaultDispatcher-worker-4 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(io.airbyte.cdk.load.task.implementor.OpenStreamTask@4e321e58) 2025-12-26 184007 destination INFO DefaultDispatcher-worker-2 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(io.airbyte.cdk.load.task.implementor.OpenStreamTask@4e321e58) 2025-12-26 184007 destination INFO main i.a.c.l.t.DestinationTaskLauncher(run):171 Setting up load pipeline 2025-12-26 184007 destination INFO DefaultDispatcher-worker-5 i.a.i.d.b.w.t.BigQueryDatabaseHandler$createNamespaces$2$1$1(invokeSuspend):157 Creating dataset if not present cacau_show_totvs 2025-12-26 184007 destination INFO DefaultDispatcher-worker-8 i.a.i.d.b.w.t.BigQueryDatabaseHandler$createNamespaces$2$1$1(invokeSuspend):157 Creating dataset if not present airbyte_internal 2025-12-26 184007 destination INFO DefaultDispatcher-worker-9 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(LoadPipelineStepTask(ObjectLoaderPartLoader, part=0)) 2025-12-26 184007 destination INFO DefaultDispatcher-worker-3 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(LoadPipelineStepTask(ObjectLoaderPartFormatter, part=0)) 2025-12-26 184007 destination INFO DefaultDispatcher-worker-6 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(LoadPipelineStepTask(ObjectLoaderPartFormatter, part=1)) 2025-12-26 184007 destination INFO DefaultDispatcher-worker-4 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(LoadPipelineStepTask(ObjectLoaderPartLoader, part=1)) 2025-12-26 184007 destination INFO DefaultDispatcher-worker-4 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(LoadPipelineStepTask(ObjectLoaderPartLoader, part=4)) 2025-12-26 184007 destination INFO DefaultDispatcher-worker-9 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(LoadPipelineStepTask(ObjectLoaderPartLoader, part=3)) 2025-12-26 184007 destination INFO DefaultDispatcher-worker-2 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(LoadPipelineStepTask(ObjectLoaderPartLoader, part=2)) 2025-12-26 184007 destination INFO DefaultDispatcher-worker-7 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(LoadPipelineStepTask(ObjectLoaderPartLoader, part=5)) 2025-12-26 184007 destination INFO DefaultDispatcher-worker-12 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(LoadPipelineStepTask(ObjectLoaderPartLoader, part=8)) 2025-12-26 184007 destination INFO DefaultDispatcher-worker-9 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(LoadPipelineStepTask(ObjectLoaderPartLoader, part=9)) 2025-12-26 184007 destination INFO DefaultDispatcher-worker-12 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(LoadPipelineStepTask(ObjectLoaderUploadCompleter, part=0)) 2025-12-26 184007 destination INFO DefaultDispatcher-worker-9 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(LoadPipelineStepTask(BulkLoaderTableLoader, part=0)) 2025-12-26 184007 destination INFO DefaultDispatcher-worker-7 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(LoadPipelineStepTask(ObjectLoaderPartLoader, part=7)) 2025-12-26 184007 destination INFO main i.a.c.l.t.DestinationTaskLauncher(run):173 Launching update batch task 2025-12-26 184007 destination INFO DefaultDispatcher-worker-2 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(LoadPipelineStepTask(ObjectLoaderPartLoader, part=6)) 2025-12-26 184007 destination INFO DefaultDispatcher-worker-2 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(io.airbyte.cdk.load.task.internal.UpdateBatchStateTask@24b3e358) 2025-12-26 184007 destination INFO main i.a.c.l.t.DestinationTaskLauncher(run):176 Launching heartbeat task 2025-12-26 184007 destination INFO DefaultDispatcher-worker-2 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(io.airbyte.cdk.load.task.internal.HeartbeatTask@6b491385) 2025-12-26 184007 destination INFO main i.a.c.l.t.DestinationTaskLauncher(run):185 Starting checkpoint update task 2025-12-26 184007 destination INFO DefaultDispatcher-worker-9 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):34 Launching TaskWrapper(io.airbyte.cdk.load.task.internal.UpdateCheckpointsTask@7cb8652e) 2025-12-26 184007 destination INFO DefaultDispatcher-worker-9 i.a.c.l.t.i.UpdateCheckpointsTask(execute):34 Starting to consume checkpoint messages (state) for updating 2025-12-26 184008 destination INFO DefaultDispatcher-worker-5 i.a.c.l.t.TaskScopeProvider$launch$job$1(invokeSuspend):36 Task TaskWrapper(io.airbyte.cdk.load.task.implementor.SetupTask@73475d0e) completed 2025-12-26 184107 destination INFO DefaultDispatcher-worker-5 i.a.c.l.s.CheckpointManager(flushReadyCheckpointMessages):148 No checkpoints to flush 2025-12-26 184207 destination INFO DefaultDispatcher-worker-2 i.a.c.l.s.CheckpointManager(flushReadyCheckpointMessages):148 No checkpoints to flush 2025-12-26 184307 destination INFO DefaultDispatcher-worker-2 i.a.c.l.s.CheckpointManager(flushReadyCheckpointMessages):148 No checkpoints to flush 2025-12-26 184407 destination INFO DefaultDispatcher-worker-2 i.a.c.l.s.CheckpointManager(flushReadyCheckpointMessages):148 No checkpoints to flush 2025-12-26 184507 destination INFO DefaultDispatcher-worker-2 i.a.c.l.s.CheckpointManager(flushReadyCheckpointMessages):148 No checkpoints to flush 2025-12-26 184607 destination INFO DefaultDispatcher-worker-2 i.a.c.l.s.CheckpointManager(flushReadyCheckpointMessages):148 No checkpoints to flush 2025-12-26 184707 destination INFO DefaultDispatcher-worker-2 i.a.c.l.s.CheckpointManager(flushReadyCheckpointMessages):148 No checkpoints to flush 2025-12-26 184807 destination INFO DefaultDispatcher-worker-2 i.a.c.l.s.CheckpointManager(flushReadyCheckpointMessages):148 No checkpoints to flush 2025-12-26 184907 destination INFO DefaultDispatcher-worker-3 i.a.c.l.s.CheckpointManager(flushReadyCheckpointMessages):148 No checkpoints to flush its been like 10 minutes airbyte didnt call the upstream not even once
k
A message from kapa.ai
I'm sorry, but there is no specific information in the knowledge sources explaining why a connection using the low-code Connection Builder would fail to call an upstream API while the destination continues to log "No checkpoints to flush." However, based on the logs you provided and the available documentation, here are some relevant insights for troubleshooting: * Destination Awaiting Data: The logs show that the destination (BigQuery) has successfully initialized, created the necessary namespaces (e.g., 
cacau_show_totvs
), and launched its internal load pipeline steps (e.g., 
ObjectLoaderPartLoader
). The repeating 
No checkpoints to flush
message indicates the destination is idling and waiting for the source to emit records or state messages [[S3 stalling](https://github.com/airbytehq/airbyte/issues/56926); [HubSpot mid-sync failures](https://github.com/airbytehq/airbyte/issues/62467)]. * Source Execution Issues: Since you noted that Airbyte has not called the upstream API, the issue likely resides in the source's execution environment. In similar cases, syncs have been reported to "hang forever" when the source fails to produce any output or if there is a discrepancy between the tester (which may run in a different network context) and the live sync worker [[Sync hangs forever BigQuery](https://github.com/airbytehq/airbyte/issues/58082)]. * Platform Stalling: There have been documented instances where syncs stall mid-way without errors in the UI, which were sometimes resolved by upgrading the Airbyte platform version [[Source halted midway](https://discuss.airbyte.io/t/2604); [Mssql CDC hangs](https://discuss.airbyte.io/t/1323)]. * Worker Resources: If your environment is constrained, ensure it meets the suggested resources (at least 8GB RAM), as low-resource environments can lead to connector execution issues [[Connector Builder Overview](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/overview#disabled-in-low-resource-mode)]. The knowledge sources do not explicitly mention a bug where renaming a stream fails to fix this behavior. I recommend checking the Source-specific logs (if available) or your upstream API's access logs to see if any connection attempts reached the server but were blocked by firewalls or network policies that differ from your testing environment.
2 Views
Open in Slack
PreviousNext
Powered by