Summary
The user is experiencing a scenario where a scheduled sync job from MSSQL to Bigquery is sending a failed sync notification after about a minute, even though the job itself is successful and loads data to the target table as expected. The issue only occurs when the job runs off the schedule, not when triggered manually.
Question
I have a scheduled sync job from MSSQL to Bigquery which has started sending a failed sync notification after about a minute, every time it runs. However the job itself is not failing, it succeeds on the first attempt every time (and is loading the data to the target table exactly as expected). It does not send a failure notification when I trigger it manually, only when running off the schedule.
Has anyone else experienced something like 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.