<@U04S8PLJWMT> I have an issue with replicating re...
# ask-ai
a
@kapa.ai I have an issue with replicating retool data in Snwoflake, The same tables don't have any issues in redshift. I tried to refresh the stream, clear the data, add a new connection with all streams, add a new connection to the only stream that is failing. where else should I look into?
k
Based on the information in the knowledge sources, here are some troubleshooting steps and considerations for your issue with replicating Retool data to Snowflake, especially since the same tables work fine with Redshift: 1. Connector and Airbyte Version: Ensure you are using the latest versions of both the Airbyte platform and the Snowflake connector. Outdated connectors or Airbyte versions can cause unexpected issues, and updating is often recommended as a first troubleshooting step. This was suggested in a similar context for Snowflake sync issues, where updating resolved some problems [Snowflake connection cancelling middle of reading records](https://discuss.airbyte.io/t/3808). 2. Splitting Large Syncs: If you are syncing a large number of tables or tables with many columns, Airbyte may hit internal limits (such as message size or resource constraints). In one case, splitting the sync into multiple connections (with fewer tables per connection) resolved the issue [Data not showing in snowflake from redshift](https://discuss.airbyte.io/t/2119). 3. Schema Refresh and Stream Catalog: If you change the destination or make schema changes, always refresh the source schema in Airbyte. Failing to do so can cause errors where the destination expects a different schema than what is being sent, leading to sync failures. Deleting and recreating the connection, or switching sync modes (e.g., from overwrite to append), can sometimes resolve schema catalog mismatches [SFTP Failing to Redshift](https://discuss.airbyte.io/t/413). 4. Logs and Error Messages: Carefully review the Airbyte sync logs for any warnings or errors, especially those related to schema, message size, or temporary tables. Sometimes, the logs may only show warnings (e.g., "tmp table has 0 files"), which can indicate underlying issues with the sync process or resource limits [Data not showing in snowflake from redshift](https://discuss.airbyte.io/t/2119). 5. Clear vs. New Connection: Using "Clear" will empty the destination tables but will not remove the tables themselves. If you have orphaned tables or files (from previous syncs or namespace changes), you may need to clean them up manually, as Airbyte does not do this automatically [Clearing your data](https://docs.airbyte.com/platform/operator-guides/clear). 6. Destination-Specific Issues: Since the sync works with Redshift but not Snowflake, there may be destination-specific constraints (e.g., data types, reserved keywords, or permissions) that are not present in Redshift. Double-check the schema compatibility and permissions in Snowflake. If you have already tried refreshing the stream, clearing data, and creating new connections (both with all streams and with only the failing stream), the next steps would be: - Split the sync into smaller groups of tables/streams. - Double-check the schema in Snowflake for compatibility issues. - Review the Airbyte logs for any subtle errors or warnings. - Ensure all connectors and Airbyte itself are up to date. If the issue persists after these steps, please provide detailed logs from the failing sync, as this can help pinpoint the root cause. If you see specific error messages or warnings, sharing those will also help in further troubleshooting.
a
@kapa.ai the solutions above have all being tried, can you look into this log: 2025-11-26 131459 replication-orchestrator INFO Sync summary: { "status" : "failed", "recordsSynced" : 0, "bytesSynced" : 0, "startTime" : 1764159204676, "endTime" : 1764159299056, "totalStats" : { "additionalStats" : { }, "bytesCommitted" : 0, "bytesEmitted" : 4828, "destinationStateMessagesEmitted" : 0, "destinationWriteEndTime" : 0, "destinationWriteStartTime" : 1764159206474, "meanSecondsBeforeSourceStateMessageEmitted" : 0, "maxSecondsBeforeSourceStateMessageEmitted" : 0, "maxSecondsBetweenStateMessageEmittedandCommitted" : 0, "meanSecondsBetweenStateMessageEmittedandCommitted" : 0, "recordsEmitted" : 10, "recordsCommitted" : 0, "recordsFilteredOut" : 0, "bytesFilteredOut" : 0, "replicationEndTime" : 1764159299053, "replicationStartTime" : 1764159204676, "sourceReadEndTime" : 0, "sourceReadStartTime" : 1764159206474, "sourceStateMessagesEmitted" : 0 }, "streamStats" : [ { "streamName" : "dhl_api_documents", "streamNamespace" : "public", "stats" : { "additionalStats" : { "sourceFieldsPopulated" : 120 }, "bytesCommitted" : 0, "bytesEmitted" : 4828, "estimatedBytes" : 0, "estimatedRecords" : 0, "recordsEmitted" : 10, "recordsCommitted" : 0, "recordsFilteredOut" : 0, "bytesFilteredOut" : 0 } } ], "performanceMetrics" : { }, "streamCount" : 1 } 2025-11-26 131459 replication-orchestrator INFO Failures: [ { "failureOrigin" : "destination", "failureType" : "transient_error", "internalMessage" : "Some streams either received an INCOMPLETE stream status, or did not receive a stream status at all: service_retool_2.dhl_api_documents\nio.airbyte.commons.exceptions.TransientErrorException: Some streams were unsuccessful due to a source error. See logs for details.", "externalMessage" : "Some streams were unsuccessful due to a source error. See logs for details.", "metadata" : { "attemptNumber" : 4, "jobId" : 59137918, "from_trace_message" : true, "connector_command" : "write" }, "stacktrace" : "io.airbyte.commons.exceptions.TransientErrorException: Some streams were unsuccessful due to a source error. See logs for details.\n\tat io.airbyte.cdk.integrations.destination.async.AsyncStreamConsumer.close(AsyncStreamConsumer.kt:217)\n\tat kotlin.jdk7.AutoCloseableKt.closeFinally(AutoCloseableJVM.kt:48)\n\tat io.airbyte.cdk.integrations.base.IntegrationRunner.runInternal(IntegrationRunner.kt:215)\n\tat io.airbyte.cdk.integrations.base.IntegrationRunner.run(IntegrationRunner.kt:119)\n\tat io.airbyte.cdk.integrations.base.IntegrationRunner.run$default(IntegrationRunner.kt:113)\n\tat io.airbyte.cdk.integrations.base.adaptive.AdaptiveDestinationRunner$Runner.run(AdaptiveDestinationRunner.kt:68)\n\tat io.airbyte.integrations.destination.snowflake.SnowflakeDestinationKt.main(SnowflakeDestination.kt:422)\n", "timestamp" : 1764159298699 }, { "failureOrigin" : "source", "internalMessage" : "Source process exited with non-zero exit code 3", "externalMessage" : "Something went wrong within the source connector", "metadata" : { "attemptNumber" : 4, "jobId" : 59137918, "connector_command" : "read" }, "stacktrace" : "io.airbyte.workers.internal.exception.SourceException: Source process exited with non-zero exit code 3\n\tat io.airbyte.container.orchestrator.worker.SourceReader.run(ReplicationTask.kt:210)\n\tat io.airbyte.container.orchestrator.worker.SourceReader$run$1.invokeSuspend(ReplicationTask.kt)\n\tat kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:34)\n\tat kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:100)\n\tat io.micrometer.core.instrument.composite.CompositeTimer.record(CompositeTimer.java:141)\n\tat io.micrometer.core.instrument.Timer.lambda$wrap$2(Timer.java:199)\n\tat datadog.trace.bootstrap.instrumentation.java.concurrent.Wrapper.run(Wrapper.java:47)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)\n\tat java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)\n\tat java.base/java.lang.Thread.run(Thread.java:1583)\n", "timestamp" : 1764159299051 } ] 2025-11-26 131459 replication-orchestrator INFO 2025-11-26 131459 replication-orchestrator INFO Closing io.micronaut.context.propagation.instrument.execution.ContextPropagatingExecutorService@3f09b882 2025-11-26 131459 replication-orchestrator INFO Closing io.micronaut.context.propagation.instrument.execution.ContextPropagatingExecutorService@161830d9 2025-11-26 131459 replication-orchestrator INFO ----- END REPLICATION ----- 2025-11-26 131459 replication-orchestrator INFO 2025-11-26 131459 replication-orchestrator INFO Closing io.airbyte.container.orchestrator.worker.io.LocalContainerAirbyteDestination@1870e28d 2025-11-26 131459 replication-orchestrator ERROR Error closing resource io.airbyte.container.orchestrator.worker.io.LocalContainerAirbyteDestination@1870e28d; recording failure but continuing. 2025-11-26 131459 replication-orchestrator INFO Closing io.airbyte.container.orchestrator.worker.io.LocalContainerAirbyteSource@347c2a1a 2025-11-26 131459 replication-orchestrator ERROR Error closing resource io.airbyte.container.orchestrator.worker.io.LocalContainerAirbyteSource@347c2a1a; recording failure but continuing. 2025-11-26 131459 replication-orchestrator INFO Closing io.airbyte.container.orchestrator.worker.RecordSchemaValidator@4cc1c39f 2025-11-26 131459 replication-orchestrator INFO Closing io.airbyte.container.orchestrator.persistence.SyncPersistenceImpl@7123f4ff 2025-11-26 131459 replication-orchestrator INFO Returning output... 2025-11-26 131500 platform INFO ----- START POST REPLICATION OPERATIONS ----- 2025-11-26 131500 platform INFO No post-replication operation(s) to perform. 2025-11-26 131500 platform INFO ----- END POST REPLICATION OPERATIONS ----- 2025-11-26 131501 platform INFO Retry State: RetryManager(completeFailureBackoffPolicy=BackoffPolicy(minInterval=PT10S, maxInterval=PT30M, base=3), partialFailureBackoffPolicy=null, successiveCompleteFailureLimit=5, successivePartialFailureLimit=1000, totalCompleteFailureLimit=5, totalPartialFailureLimit=20, successiveCompleteFailures=5, successivePartialFailures=0, totalCompleteFailures=5, totalPartialFailures=0) Backoff before next attempt: 13 minutes 30 seconds 2025-11-26 131501 platform ERROR Failing job: 59137918, reason: Job failed after too many retries for connection 3a6a90f6-2293-4c2f-9e84-5eec2185b20e
k
A message from kapa.ai
Based on the log you provided, the sync is failing with the following key errors: - Destination error:
"Some streams either received an INCOMPLETE stream status, or did not receive a stream status at all: service_retool_2.dhl_api_documents\nio.airbyte.commons.exceptions.TransientErrorException: Some streams were unsuccessful due to a source error. See logs for details."
- Source error:
"Source process exited with non-zero exit code 3"
"Something went wrong within the source connector"
- No records committed: The sync emitted 10 records but committed 0 to Snowflake. ### What does this mean? - The error is classified as a transient error on the destination side, but the root cause appears to be a source connector failure (exit code 3). - The destination (Snowflake) is reporting that it did not receive a complete or valid stream from the source, which matches the source process exiting unexpectedly. - This pattern is similar to other issues where the source connector fails, causing the destination to report incomplete or missing data, and ultimately no records are written [source-jira sync hangs forever](https://github.com/airbytehq/airbyte/issues/58082), [source-zendesk-support ticket_comments not syncing](https://github.com/airbytehq/airbyte/issues/52133). ### What should you do next? 1. Check the Source Connector Logs: The most actionable step is to look at the detailed logs for the source connector (Retool in your case). The exit code 3 is a generic failure, and the root cause (such as a schema issue, API error, or data problem) should be visible in the source logs. 2. Review Data and Schema: Since the same tables work in Redshift but not in Snowflake, check for: - Data types or values in the failing stream that might not be compatible with Snowflake. - Schema mismatches or reserved keywords in Snowflake. 3. Connector Version and Updates: Ensure both your source and destination connectors are up to date, as some transient errors and stream handling bugs have been fixed in recent versions [Data not showing in snowflake from redshift](https://discuss.airbyte.io/t/2119). 4. Resource Constraints: While your sync is small (10 records), sometimes resource issues or temporary network/API failures can cause transient errors. If this is a recurring pattern, try restarting the sync or the Airbyte instance. 5. Retry and Split Streams: If the issue is isolated to a single stream, try syncing only that stream in a new connection to isolate the problem further (which you mentioned you already tried). ### Summary The failure is due to the source connector exiting with an error, which then causes the destination (Snowflake) to report an incomplete stream and commit no records. The next step is to review the detailed source connector logs for the specific error message that caused the exit code 3. If the logs do not provide enough information, consider updating your connectors and Airbyte version, and double-check the schema and data for compatibility issues. If you can provide the relevant section of the source connector logs, I can help analyze the root cause further.
a
@kapa.ai aibyte is only able to get only 10 IDs and only the same ones. I want to mention that the stream was working fine 3 days ago
k
A message from kapa.ai
If Airbyte is only able to retrieve 10 IDs (and always the same ones), and the stream was working fine a few days ago, this strongly suggests an issue with the source API or connector configuration, rather than with Snowflake or the destination. Here are the most likely causes based on the knowledge sources: 1. API Endpoint Limitation or Change Some APIs have endpoints that only return a limited number of records (e.g., 10 or 10,000), or have recently changed their behavior. For example, in the Hubspot connector, using the
/recent
endpoint limited results to 10,000 records, and the connector logic could cause it to always fetch the same subset if state handling or endpoint selection is incorrect. A similar issue could be happening with your source, especially if the API or connector was updated recently or if the endpoint being used is not paginating correctly. Review the connector’s logic and the API documentation to ensure the correct endpoint and pagination are being used [Hubspot engagements stream -- /recent vs /paged endpoint](https://discuss.airbyte.io/t/3718). 2. State Handling or Cursor Issue If the connector is not updating its state or cursor correctly, it may repeatedly fetch the same records. This can happen if the cursor field is not being updated, or if the API does not support proper incremental sync and the connector is not handling pagination or state checkpointing as expected. This is a common cause for only seeing the same records on each sync [Incremental sync requirements](https://docs.airbyte.com/platform/1.8/connector-development/connector-builder-ui/incremental-sync). 3. Source API Data Change If the source data itself has changed (e.g., only 10 records now match the query or filter), Airbyte will only sync those. Double-check the source system to ensure there are more records available and that no filters or permissions have changed. 4. Connector or API Error If the connector or API is returning errors or incomplete data, Airbyte may only process a partial result set. Review the Airbyte logs for any warnings or errors from the source connector. Recommended Actions: - Check if the source API or connector was updated or changed in the last few days. - Review the connector configuration, especially pagination and cursor settings. - Inspect the Airbyte logs for the source connector for any errors or warnings. - Confirm that the source API is returning more than 10 records when queried directly (e.g., via Postman or curl). - If the connector uses state, try resetting the connection state in Airbyte and running a full refresh. If you provide the connector type and any recent changes, I can help with more targeted troubleshooting steps. If the issue persists and none of the above applies, the knowledge sources do not provide a more specific solution for this exact scenario.
a
@kapa.ai I found the solution, one of the column (probably a link) was way too long to be extracted
k
A message from kapa.ai
Thank you for sharing your solution. Your finding aligns with known issues in Airbyte where very long string or JSON fields can cause extraction or sync failures, especially when syncing to destinations like Snowflake or Redshift. For example, Redshift has a 65k bytes limit for individual string fields within a
SUPER
object, and fields exceeding this limit are dropped before insertion, which can result in missing or incomplete records in the destination. Similar issues have been reported with other connectors when handling large fields, leading to sync failures or only partial data being extracted and committed [Issue with long JSON field and mysql source](https://discuss.airbyte.io/t/1566). If you encounter this again, consider truncating or excluding excessively long fields in your source schema, or adjusting the connector configuration to handle such cases. This approach can help ensure successful extraction and syncing of your data.