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

SendGrid connector fails, even though log says successful #4801

Closed
rahimnathwani opened this issue Jul 17, 2021 · 3 comments · Fixed by #4839
Closed

SendGrid connector fails, even though log says successful #4801

rahimnathwani opened this issue Jul 17, 2021 · 3 comments · Fixed by #4839

Comments

@rahimnathwani
Copy link

Environment

  • Airbyte version: 0.27.3-alpha
  • OS Version / Instance: Linux 4.19.0-17-cloud-amd64 checkin catalogs #1 SMP Debian 4.19.194-1 (2021-06-10) x86_64 GNU/Linux
  • Deployment: docker
  • Source Connector and version: Sendgrid 0.2.5
  • Destination Connector and version: Postgres 0.3.6
  • Severity: Critical
  • Step where error happened: Sync job

Current Behavior

Sync job fails and gives up after 3 tries, even though the logs say 'completed successfully'. And no data gets written to my target.

Expected Behavior

Sync job should complete and populate my database.

Logs

logs-168-0.txt

@rahimnathwani rahimnathwani added the type/bug Something isn't working label Jul 17, 2021
@sherifnada sherifnada added area/connectors Connector related issues priority/high High priority labels Jul 17, 2021
@sherifnada
Copy link
Contributor

sherifnada commented Jul 17, 2021

@rahimnathwani is the UI showing the job status as succeeded or failed? The logs are misleading here: Airbyte makes a best effort to sync data in the case of a failure. The "success" part is referring specifically to normalization.

If the job status in the UI or API is showing successful, that's a real issue.

I'm attempting to reproduce the connector failure issue on my side but haven't found success so far. Will update you as soon as I can repro

@rahimnathwani
Copy link
Author

In the UI it's showing failure.

@sherifnada
Copy link
Contributor

fixed in #4839

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.

3 participants