-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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 Amplitude: connector throws 404 when dont have any data #6375
Comments
File "/airbyte/integration_code/source_amplitude/api.py", line 160, in read_records |
Hi @blotouta2 from Amplitude docs, can you double check the start/end date you'd used?
|
Yes, i used start and end date from the current month. |
@blotouta2 and you can confirm there is data in the account? |
@sherifnada dashboard shows that we have 256 events since last 1 month |
I think the correct way to handle a 404 then is to log it and not fail the connector |
We just merged this feature into master and released a new version of the connector. Upgrade your connector to version 0.1.3 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! |
@blotouta2 can you check the new version of this connector and test it? |
Enviroment
OS Version / Instance: EC2 micro.a4
Memory / Disk: 12Gb / 256Tb SSD
Deployment: Kubernetes Airbyte
Version: 0.28.1-alpha
Source name/version: Amplitude 0.1.0
Destination name/version: Postgres
Current Behavior
I'm trying to sync for the first time and the process has been failed due to 404 errors from client api .
Expected Behavior
Tell us what should happen.
Logs
If applicable, please upload the logs from the failing operation.
For sync jobs, you can download the full logs from the UI by going to the sync attempt page and
clicking the download logs button at the top right of the logs display window.
LOG
Steps to Reproduce
Are you willing to submit a PR?
Remove this with your answer.
The text was updated successfully, but these errors were encountered: