Summary
Some schedules for ingesting data from MySQL and MongoDB in Airbyte fail to start in the first attempt with a ScheduleToStart timeout of about 60 minutes, while other schedules start normally. Investigating the root cause of this issue.
Question
message=‘activity ScheduleToStart timeout’, timeoutType=TIMEOUT_TYPE_SCHEDULE_TO_START
I have the issue for ingestion data from MySQL and MongoDB with airbyte that some schedule failed to start in first attempt (schedule to start timeout about 60min) but other schedule able to start normally. What is the root cause in this
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.