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

Issue with Marketo Source #12732

Closed
Tracked by #14056
kyle-cheung opened this issue May 10, 2022 · 4 comments
Closed
Tracked by #14056

Issue with Marketo Source #12732

kyle-cheung opened this issue May 10, 2022 · 4 comments
Labels
autoteam community team/tse Technical Support Engineers type/bug Something isn't working

Comments

@kyle-cheung
Copy link

Environment

  • Airbyte version: example is 0.36.65-alpha
  • OS Version / Instance: AWS EC2 t2.large
  • Deployment: docker
  • Source Connector and version: Marketo 0.1.3
  • Destination Connector and version: Snowflake 0.4.25
  • Severity: High
  • Step where error happened: Sync job

Current Behavior

My Marketo sync fails when I have all 93 tables in the schema selected. However, if I’m only replicating the tables: activity_change_data_value, lead, program tables, the sync succeeds. Not sure why this is happening. Any help is appreciated!
logs-7696 (1).txt

I got some help in Discourse and was told to submit an issue. After testing out Harshith's suggestion to try and sync another random 5 set of tables and reverting back to the original 3 tables. The sync is no longer successful.
logs-7830 (2).txt

The sync also takes extremely long back when it was successful. The first sync of just the 3 tables noted above took 1.5 hours, and subsequent incremental syncs took 2.5 hours each. However, it's interesting to note that on failed sync with 93 tables the full run only took less than a minute.

@kyle-cheung
Copy link
Author

I actually suspect this might be due to the Marketo rate limits, but I wonder how Fivetran gets around this issue? Because we never encounter this through them

@kyle-cheung
Copy link
Author

Just adding on the latest log from an almost successful run
logs-7871.txt

@kyle-cheung
Copy link
Author

Just upgraded to 0.38.1-alpha and it is still failing:
logs-8024.txt

@davydov-d
Copy link
Collaborator

This looks the same as #10191 and #9332.
It is temporary fixed and will be reworked in #14149

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
autoteam community team/tse Technical Support Engineers type/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants