First sync successful , next syncs 0 bytes no records

  • Is this your first time deploying Airbyte?: Yes
  • OS Version / Instance: Ubuntu 20.04LTS
  • Memory / Disk: you can use something like 32GB / 3 TB
  • Deployment: Are you using Docker or Kubernetes deployment? Docker compose
  • Airbyte Version: What version are you using now? 0.40.18
  • Source name/version: PostgreSQL 1.0.22
  • Destination name/version: Snowflake 0.1.24
  • Step: The issue is happening during sync, creating the connection or a new source? Issue happening after original sync
  • Description:
    I have two pipelines which have the same issue. Both source databases are postgres 12 databases.

When doing an original sync everything gets synced/normalized perfectly onto snowflake.

The issue I am having is when doing subsequent syncs the sync takes a while and yet it shows no new records no bytes downloaded even tho the database is fully active.

All tables in each database have a primary key.
Attached is a screenshot to show the syncs as well as a log from one of the sync that returned nothing

72bd354c_2061_42f1_a6ee_8a86e496aff5_logs_8_txt (1).txt (195.5 KB)

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
The Community Assistance Team

Hey @Alexandre_Voyer, thanks for being patient with us - we’ve had a large influx of messages due to Hacktoberfest and are working through them as fast as we can. I see that you posted on Slack on Monday - let’s get back to that thread and keep the discussion going there. Please keep to the convention of one question per thread/platform in the future - this helps keep our team organized and prevents different team members working on the same question without being aware. Thank you!