Issue with cron syncs after restoring Airbyte OSS DB


After restoring Airbyte OSS DB into another EC2 instance, cron syncs are not executing properly. User suspects that the cron jobs that did run correctly were modified after the restore. User is seeking help to find the state of the scheduled jobs in the DB or OS.


For Airbyte OSS, I backed up the DB and restored it into another EC2 instance and I ran into a problem that most of my cron synch’s did not execute.
I’m thinking that the couple that did run correctly on schedule were modified after the restore and during the save did something to fully schedule them.
Has anyone else run into this after a DB restore or know where in the DB or OS I can find the state of the scheduled jobs?

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

["airbyte-oss", "db-restore", "cron-syncs", "scheduled-jobs", "ec2-instance"]