@kapa.ai my airbyte connector is failing almost every run with the following error. what can i do to fix this? 2024-09-24 195117 normalization > 21 of 26 OK created table model lc_connection.item_item_prices....................................... [SELECT 33570 in 1.60s] 2024-09-24 195118 normalization > 23 of 26 OK created table model lc_connection.sale_sale_metadata..................................... [SELECT 21733 in 1.02s] 2024-09-24 195118 normalization > 22 of 26 OK created table model lc_connection.item_item_itemshops.................................... [SELECT 33570 in 1.92s] 2024-09-24 195118 normalization > 24 of 26 START table model lc_connection.item_item_prices_itemprice.................................. [RUN] 2024-09-24 195118 normalization > 25 of 26 START table model lc_connection.saleline_saleline_taxcategory............................... [RUN] 2024-09-24 195119 normalization > 26 of 26 START table model lc_connection.item_item_itemshops_itemshop................................ [RUN] 2024-09-24 195119 normalization > 25 of 26 OK created table model lc_connection.saleline_saleline_taxcategory.......................... [SELECT 2183 in 0.74s] 2024-09-24 195119 normalization > 24 of 26 OK created table model lc_connection.item_item_prices_itemprice............................. [SELECT 100710 in 1.14s] 2024-09-24 195120 normalization > 26 of 26 OK created table model lc_connection.item_item_itemshops_itemshop........................... [SELECT 67140 in 1.04s] 2024-09-24 195120 normalization > Finished running 26 table models in 21.94s. 2024-09-24 195120 normalization > Completed successfully 2024-09-24 195120 normalization > Done. PASS=26 WARN=0 ERROR=0 SKIP=0 TOTAL=26 2024-09-24 195122 platform > Terminating normalization process... 2024-09-24 195122 platform > Normalization process successfully terminated. 2024-09-24 195122 platform > Normalization executed in 1 minute 9 seconds for job 49069. 2024-09-24 195122 platform > Normalization summary: io.airbyte.config.NormalizationSummary@6b46618e[startTime=1727207412263,endTime=1727207482094,failures=[],additionalProperties={}] 2024-09-24 195122 platform > 2024-09-24 195122 platform > ----- END DEFAULT NORMALIZATION ----- 2024-09-24 195122 platform > 2024-09-24 195915 platform > Retry State: RetryManager(completeFailureBackoffPolicy=BackoffPolicy(minInterval=PT10S, maxInterval=PT30M, base=3), partialFailureBackoffPolicy=null, successiveCompleteFailureLimit=5, totalCompleteFailureLimit=10, successivePartialFailureLimit=1000, totalPartialFailureLimit=20, successiveCompleteFailures=0, totalCompleteFailures=0, successivePartialFailures=1, totalPartialFailures=1) Backoff before next attempt: 0 seconds 2024-09-24 195915 platform > Failing job: 49069, reason: Connection Check Failed 8f501c86-7204-4cfc-99b7-19e069da9570

Based on the logs you provided, it seems like the normalization process completed successfully but the connection check failed. This could be due to a variety of reasons such as network issues, incorrect credentials, or changes in the data source. Here are a few steps you can take to troubleshoot this issue: 1. Check your connection credentials: Make sure the credentials you provided for your source and destination are correct. This includes the host URL, username, password, database name, etc. 2. Check your network: Ensure that your Airbyte instance can reach the source and destination. This could involve checking firewall rules, network access permissions, etc. 3. Check the source and destination systems: If you're using a database as a source or destination, ensure that it's up and running without any issues. If there were any recent changes in the schema or data types, it could potentially cause issues. 4. Upgrade Airbyte and connectors: If you're using an older version of Airbyte or its connectors, consider upgrading to the latest version. There have been cases where upgrading Airbyte or the connectors resolved similar issues ([source](https://discuss.airbyte.io/t/1273)). 5. Check for incompatible changes: If the issue started occurring after an upgrade or change in your setup, it could be due to some incompatible changes. For example, some changes might not be backward compatible ([source](https://discuss.airbyte.io/t/1273)). If none of the above steps help, consider reaching out to the Airbyte community on their [forum](https://discuss.airbyte.io/) or [GitHub](https://github.com/airbytehq/airbyte/issues) for further assistance.

@kapa.ai is airbyte 1.0 a stable version to upgrade from

0.63.4

?

A message from kapa.ai

Based on the knowledge sources provided, there is no specific information about the stability of Airbyte 1.0 or its suitability for upgrading from version 0.63.4. However, it's generally recommended to use the latest version of software as it usually includes bug fixes, performance improvements, and new features. Before upgrading, you should check the [release notes](https://docs.airbyte.com/release_notes) and [migration guides](https://docs.airbyte.com/integrations/sources/zendesk-talk-migrations#zendesk-talk-migration-guide) to understand what changes to expect and how to handle them. Also, remember that upgrades in Airbyte require temporarily turning off the system. During upgrades, Airbyte will attempt to upgrade some connector versions based on certain rules. If a connector is used, it will NOT be upgraded to avoid disrupting working workflows. If you want to upgrade a specific connector, do so in the settings page in the webapp ([source](https://docs.airbyte.com/operator-guides/upgrading-airbyte)). Lastly, before upgrading, ensure that any connector currently part of an active connection will still be supported after the upgrade. If any connector fails this check, the upgrade will be aborted and you will need to upgrade those connectors from the UI before the platform itself can be upgraded ([source](https://docs.airbyte.com/understanding-airbyte/airbyte-protocol-versioning#safeguards)). If you encounter any issues during the upgrade, you can reach out to the Airbyte community on their [forum](https://discuss.airbyte.io/) or [GitHub](https://github.com/airbytehq/airbyte/issues) for assistance.

@kapa.ai the latest run-ab-platform.sh download shows version

0.64.7

instead of

1.0

..why is that?

A message from kapa.ai

The

run-ab-platform.sh

script downloads the latest version of Airbyte that is available at the time of execution. If it's showing version

0.64.7

, it means that this is the latest version available at the time you ran the script. The version

1.0

you mentioned might not have been released yet, or there could be a delay in its availability. It's also possible that

1.0

is a major release with significant changes, and the Airbyte team is performing additional tests before making it available for download. You can always check the latest version of Airbyte and its release notes on the [Airbyte GitHub repository](https://github.com/airbytehq/airbyte). If you believe there's an issue with the version being downloaded, consider reaching out to the Airbyte community on their [forum](https://discuss.airbyte.io/) or [GitHub](https://github.com/airbytehq/airbyte/issues) for further assistance.