-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FB Marketing: lookback window logic not functioning correctly #2828
Comments
Insights streams have loopback logic when it requests data from the API at Line 379 in 99f1448
, but then it performs additional filtration as part of general read logic for all streams with states (the state doesn't take into account 28 days from the past): Line 159 in 99f1448
Should be easy fix - implement custom read for InsightStream. Total: 4hours |
Great stuff! Im still manually reseting & rerunning this connection every morning. Can’t wait for a fix to be released. |
@MaxKrog we should have this released very soon -- it's in the current sprint! |
We just merged this bug into master and released a new version of the connector. Upgrade your connector to version 0.2.4 and get started. To upgrade your connector version, go to the admin panel in the left hand side of the UI, find this connector in the list, and input the latest connector version. Please let us know if you have any further questions. Enjoy! |
This is great news! Thanks for all the hard work. |
Expected Behavior
Insights data synced from facebook marketing could be updated up to 28 days after its generation. Therefore I expect the Airbyte connector to pull data from the past 28 days even with incremental sync.
Current Behavior
A user @MaxKrog has reported that the connector is only inserting records for the new days, not the past 28 days.
Logs
logs-9-0.txt
Slack conversation: https://airbytehq.slack.com/archives/C01MFR03D5W/p1617701356298100
Steps to Reproduce
Severity of the bug for you
High -- missing data
Version Information
see logs
The text was updated successfully, but these errors were encountered: