Trouble with Amazon Ads source stream 'sponsored_products_report_stream'

Slack Knowledge Base Q&A Connector Questions
, , , ,
1

Summary

User is facing issues with the Amazon Ads source stream ‘sponsored_products_report_stream’ in Airbyte connector, receiving HTTP 400 status codes and no data rows. Looking for feedback or suggestions to resolve the problem.


Question

Hi <#C021JANJ6TY|ask-community-for-troubleshooting>,

I’m having trouble using the Amazon Ads source, specifically the stream “sponsored_products_report_stream”. Despite knowing there should be data, I’m not receiving any rows. The logs show numerous HTTP 400 status codes, as seen in the attached image. I have also attached the logs for reference.
I would greatly appreciate any feedback or suggestions on how to resolve this issue. Has anyone experienced a similar problem?

P.S.: Last week I created a ticket regarding this issue, but I haven’t received any response yet.

Thank you!


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

["amazon-ads", "source-connector", "sponsored-products-report-stream", "http-400", "logs"]
2

Have you tried to check those urls after Backing off _download_report(...) for 1.0s (requests.exceptions.HTTPError: 400 Client Error: Bad Request for url:
simply by opening them in a browser as they occur?
Maybe you can get some details what is wrong

3

Good idea, thank you!

I just did. And I can download the Amazon SP report with Data! So it means actually Amazon is generating the report successfully, but Airbyte is not getting it and failing…

4

maybe backoff mechanism is not sufficient and report is available to download a bit later after 5 tries

2024-07-12 20:23:12  source   &gt; Backing off _download_report(...) for 0.9s
2024-07-12 20:23:13  source   &gt; Backing off _download_report(...) for 3.5s
2024-07-12 20:23:17  source   &gt; Backing off _download_report(...) for 1.8s
2024-07-12 20:23:19  source   &gt; Giving up _download_report(...) after 5 tries
2024-07-12 20:23:19  source   &gt; Backing off _try_read_records(...) for 1.2s```
it would be good to possibility to configure optionally those timeout for situations like this
5

it looks like changes are required in connector and checking if increasing timeouts will solve this issue

6

Interesting. Who would I have to reach out to to accomplish this?

7

You can add an issue here https://github.com/airbytehq/airbyte/issues
On the page https://github.com/airbytehq/airbyte/issues/new/choose I can see a template (see attached screenshot)
Use [source-amazon-ads] or Source Amazon Ads: at the beginning of a title

8

I opened the issue, thank you!

https://github.com/airbytehq/airbyte/issues/42118