Good day. Thanks for this community to troubleshoot. I have found a lot of useful information in other people's posts but nothing on this issue that I am encountering. I'd appreciate any insight into the scheduling that's going awry. Is this your first time deploying Airbyte: No Deployment: Kubernetes Airbyte Version: 0.35.42-alpha Source: Occurs with Airbyte Facebook Marketing and custom Python HTTP connector Destination: Redshift via S3 Source name/version: airbyte/source-facebook-marketing 0.2.37 / custom HTTP connector Destination name/version: airbyte/destination-redshift 0.3.23 Description: Configured connections execute as designed when initiated manually but do not execute according to the Replication Frequency specified on the connector. For instance, a custom HTTP connector ran successfully at 1321 on 18 March with Frequency = 8 hours but has not executed in the interim. This is also occurring with an Airbyte Facebook Marketing source and the same destination.

Hey can you help with the scheduler logs ?

Thanks. These are the logs from the pod that was an issue. I killed the scheduler pod with the issue, and the pod that started back up is working as expected with respect to scheduling. I'll check back on the thread if it happens again.

@Harshith (Airbyte) @Jason Wiener I have the same issue. do you have any solution for this?

@Alex Bondar Bouncing the scheduler pod in kube got the scheduled jobs running again and they've kept going so far without incident. Do your scheduler logs show the same kind of errors mine did?

@Jason Wiener yes