Airbyte - Notice history

We tracked the source of the incident to one of our vendors and it has now been resolved. If you see errors, please retry your syncs.

Update:

The errors on the failure will look like this:

`Failure Origin: airbyte_platform, Message: An internal Airbyte error has occurred. This sync will need to be retried.`

`Additional Failure Information: Setting attempt to FAILED because the temporal workflow for this connection was restarted, and existing job state was cleaned.`

The team has pushed an update that will allow resets to correctly remove data in the final tables for streams with Incremental | Append sync modes.

If you see duplicate data in your destination and you had Incremental | Append sync, running a reset will remove those duplicates and run a fresh, from scratch, sync. Please reach out to Cloud support via in-app chat or in-app webform if you need to run a reset due to this issue and credits will be reimbursed.

We just resolved the issue!

No action on the user end is needed on affected syncs to start again.

Thank you all for your patience as we worked this out.

We have implemented a fix and currently monitoring the result.

We just resolved the issue. Thank you for your patience while we worked to fix this issue.

We just resolved the issue for both Cloud and OSS. Frequency changes should are now working as expected.

Thank you all for your patience as we resolved this.

The root cause has been identified (currently affecting OSS and Cloud users) and we are working on a fix now.

Updates to come as we finish up and deploy the fix.

After monitoring the implemented fix we have confirmed this issue has been resolved.

If you were affected by this issue, we recommend running a reset to ensure your data is accurate and up-to-date.

Please reach out to Airbyte Technical Cloud support if you have questions!

Thank you for your patience and apologies for any inconvenience this issue has caused.

We are now testing a solution internally and currently monitoring the result.

Updates to come here when all tests pass and we deploy to cloud. Thanks for your patience as we work to resolve this!

Update: This issue is affecting destinations BigQuery + BigQuery (denormalized typed struct).

Workaround for both destinations: Use the default dataset setup for your BigQuery destination settings, not the custom namespace. In this case, we suggest resesting and syncing fresh.

More updates to come as we continue towards a resolution.

Workaround identified: Use the default dataset setup for your BigQuery destination settings, not the custom namespace.

More updates to come as we continue towards a resolution.

We just resolved the issue! We experienced unexpected network traffic that overloaded our system which led to some unique errors. We have addressed the issue by bolstering our infrastructure and enabled two additional IP addresses. If you have a database connector or other connector that requires IPs to be whitelisted, you may need to make sure that all of the following IP addresses are whitelisted : 34.106.109.131 | 34.106.196.165 | 34.106.60.246 Sorry for the inconvenience and we appreciate your understanding.

A fix has been pushed and we are monitoring the update.