You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
Environment
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.
The text was updated successfully, but these errors were encountered: