We have a self hosted airbyte instance and we are seeing gaps in our connector logs. We are trying to connect to Postgres with connector version 3.8.1 and ingest data. The connector is set up to read data. It successfully runs the discovery mode and reads the schema but then pauses for 10 minutes before exiting without processing any data. If there was no data to read we would expect it to exit immediately? Does anyone have similar experience with the Postgres connector and how did they resolve it. The postgres db is implemented by a 3rd party using neon. Thanks

hard to tell, go into container level and see what is printed in stdout and if there is any clear problems with the source connector container