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

Source Marketo: leads stream always fails #10191

Closed
Tracked by #14056
KhristinaR opened this issue Feb 8, 2022 · 2 comments
Closed
Tracked by #14056

Source Marketo: leads stream always fails #10191

KhristinaR opened this issue Feb 8, 2022 · 2 comments
Assignees

Comments

@KhristinaR
Copy link

KhristinaR commented Feb 8, 2022

Environment

  • Airbyte version: 0.35.17-alpha
  • OS Version / Instance: n1-standard-2
  • Deployment: GCP (Compute Engine)
  • Source Connector and version: Marketo 0.1.3
  • Destination Connector and version: BigQuery 0.6.7
  • Severity: Critical
  • Step where error happened: Sync job

Current Behavior

The ''leads'' stream fails every time in 30 sec. There are no issues with activities stream or with programs stream (a separate pipeline). The expected output is 333000 rows. No issues with API limits as Matillion can load the same data from the same API endpoints.

Expected Behavior

successful synch

Logs

The logs are in the attachment.

Steps to Reproduce

logs-365.txt

@KhristinaR KhristinaR added needs-triage type/bug Something isn't working labels Feb 8, 2022
@KhristinaR KhristinaR changed the title Source Marketo: leads pipeline always fail Source Marketo: leads pipeline always fails Feb 8, 2022
@KhristinaR KhristinaR changed the title Source Marketo: leads pipeline always fails Source Marketo: leads stream always fails Feb 8, 2022
@bleonard bleonard added autoteam team/tse Technical Support Engineers labels Apr 26, 2022
@CyprienBarbault
Copy link
Contributor

We used to have this issue but it doesn't happen anymore after updating Airbyte to v0.37.0-alpha

@davydov-d
Copy link
Collaborator

this issue has been temporary resolved, a long term fix should be implemented in #14149

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Status: No status
Development

No branches or pull requests

7 participants