Klaviyo Connector - Replication Start Date from Source Config Not Updating with Each Sync

  • Is this your first time deploying Airbyte?: Yes
  • OS Version / Instance: Ubuntu, Amazon Linux 2
  • Memory / Disk: you can use something like 100Gb
  • Deployment: Docker
  • Airbyte Version: 0.41
  • Source name/version: Klaviyo
  • Destination name/version: Redshift
  • Step: sync
  • Description:

Hi everyone,

I am having an issue with the Klaviyo source connector in Airbyte. Specifically, I have set the replication start date in the source configuration to 2023-03-01T00:00:00 and configured the connector to run the sync every 3 hours. However, I noticed that each time the sync runs, it calls the API for the same start time from the source config, not the “max(datetime)” from the destination table.

I did find a workaround by using an API call to update the replication start date programmatically. However, I am interested in learning more about best practices for handling this kind of task with Airbyte. Is there something else I need to install or configure to ensure that the Klaviyo source connector is using the “max(datetime)” from the destination table as the replication start date with each sync?

Any help or advice would be greatly appreciated. Thank you in advance!

Best regards,

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