Skip to content
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

Closed
sherifnada opened this issue Apr 9, 2021 · 5 comments · Fixed by #3395
Closed

FB Marketing: lookback window logic not functioning correctly #2828

sherifnada opened this issue Apr 9, 2021 · 5 comments · Fixed by #3395

Comments

@sherifnada
Copy link
Contributor

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
image (2)
image (1)
Slack conversation: https://airbytehq.slack.com/archives/C01MFR03D5W/p1617701356298100

Steps to Reproduce

  1. Setup FB marketing connector to replicate incrementally
  2. on the second sync, the connector does not replicate data from the past 28 days

Severity of the bug for you

High -- missing data

Version Information

see logs

@sherifnada sherifnada added type/bug Something isn't working area/connectors Connector related issues labels Apr 9, 2021
@keu
Copy link
Contributor

keu commented May 3, 2021

Insights streams have loopback logic when it requests data from the API at

buffered_start_date = self._state.subtract(days=self.buffer_days)

, 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):

Should be easy fix - implement custom read for InsightStream.
2h - implementation
2h - testing

Total: 4hours

@MaxKrog
Copy link
Contributor

MaxKrog commented May 3, 2021

Great stuff! Im still manually reseting & rerunning this connection every morning. Can’t wait for a fix to be released.

@sherifnada
Copy link
Contributor Author

@MaxKrog we should have this released very soon -- it's in the current sprint!

@vitaliizazmic
Copy link
Contributor

@MaxKrog

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!

@MaxKrog
Copy link
Contributor

MaxKrog commented May 14, 2021

This is great news! Thanks for all the hard work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants