Scheduled sync not triggering automatically after EC2 replacement


Airbyte instance running on EC2 with configurations table externalized to RDS is not triggering scheduled sync automatically after EC2 replacement. Workaround involves manually starting and stopping each scheduled sync connection. Cron expression is persisted but not working until manual intervention.



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
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.

Join the conversation on Slack

["scheduled-sync", "ec2", "rds", "cron-expression", "automatic-trigger"]