Summary
The user reports an issue where scheduled syncs do not trigger automatically after the EC2 instance is replaced by an Auto Scaling Group, despite the cron expression being persisted. A manual intervention is required to restart the sync connections for them to function normally.
Question
Hi,
Airbyte version:0.50.30
Deployment: Docker compose
We have an Airbyte instance running on EC2 , with airbyte configurations table externalised to RDS , Whenever current EC2 is terminated and replaced by ASG , the scheduled sync is not getting triggered automatically even though the cron expression is getting persisted.
Workaround: have to manually start and stop each scheduled sync connection, after that cron starts working normally
https://github.com/airbytehq/airbyte/issues/34407
Has anyone else faces this issue?
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.