Hi Team ! :octavia-wave: I was trying to set up th...
# replication-troubleshooting
m
Hi Team ! octavia wave I was trying to set up the Adjust connector (alpha) and the below error pops up no matter the setup of the source. The equivalent API calls succeed 🤔 The issue occurrs with fetching the schema of the source sadparrot Screen below 🔽 It’d be so grateful on any insight! We’ve got the newest version of Airbyte.
image.png
image.png
r
You will see more errors in the docker logs, can you paste from the container
m
@Monika Bednarz I got the same error for a another connector so I can say that this error is not related to Adjust. I asked the same question on Slack and Airbyte discuss but haven’t gotten any response yet. In my case it works with the version 0.40.14 but get this error in the later versions.
r
Its a generic error, will be shown if its not able to fetch the schema so its not connector specific at all
not much in there, it just says - Something went wrong in the connector. See the logs for more details
check if your API_TOKEN is valid, as it tries to make a call to https://dash.adjust.com/control-center/reports-service/ this endpoint
there might be an error, hitting the service and hence its throwing an non JSON response
m
I am simultaneously making calls to the API with this token and all of them give 200 😞
r
Are you saying that you are reusing the token across Airbyte and other clients which you have, running into rate limit issues
m
No, when the connection failed, I tried to make a few calls with parameters I need (~5) to see if it’s access issues. It’s not 😞
m
@Monika Bednarz here’s the forum thread I opened for (probably) the same error. Someone from Airbyte returned today. You may want to follow it
thanku 1
🙏 1
And if you find a solution please let me know about it 🙂
u
Hello Monika Bednarz, it's been a while without an update from us. Are you still having problems or did you find a solution?
m
Hey Marcos. The issue is still there, since there were no updates to the connector. The schema fetching failed so we were testing other solutions. There is little to no visibility on the root cause on our side. Have there been any investigations or logged issues coresponding to this?
s
Hey @Monika Bednarz sorry to hear you’re still facing this issue. At the moment, we haven’t looked investigated this connector, but I’m looking into the issue now. The failure of schema fetching could be due to many reasons: it could be a regression of the connector compared to the API or it could an issue with our platform (for instance the issue that Murat posted about above with the Zuora source connector, which has been fixed at this point) Are you using the latest version of Airbyte and the connector?
Additionally, if you could make a github issue about this specific connector and link it here, it might be easier to track for our team. Let me know if that's too much trouble though.
m
Done! Here. 😉
s
Thanks Monika, sorry to hear that you’re still facing this issue. We’ll see if we can reproduce the issue. Thanks for your patience 🙏