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 with links on the side, if I click the link of the logs manually, I can download a JSON file with the data. I would greatly appreciate any feedback or suggestions on how to resolve this issue

I'm sorry to hear that you're having trouble with the Amazon Ads source in Airbyte. Based on the knowledge sources provided, I can't find a direct solution to your problem. However, I can suggest a few general troubleshooting steps: 1. Check your connector version: Make sure you're using the latest version of the Amazon Ads connector. Updates often include bug fixes and improvements. For example, in one of the [Github issues](https://github.com/airbytehq/airbyte/issues/37496), a user was advised to check the latest version of the Amazon Ads connector as it had fixes for some endpoints. 2. Check your configuration: Ensure that your source configuration is correct. In one of the [Github issues](https://github.com/airbytehq/airbyte/issues/33963), a user reported missing data in a stream and questioned if there was something wrong with their source configuration. 3. Check the logs: You mentioned that you're seeing HTTP 400 status codes in the logs. These usually indicate a client-side error, such as a bad request. Try to understand what these errors are indicating. 4. API permissions: Ensure that the API permissions for your Amazon Ads account are correctly set up. In a [forum post](https://discuss.airbyte.io/t/912), a user was advised to check if they could consume the Amazon Ads API with the same set of credentials using Postman or

curl

, suggesting that API permissions could be a potential issue. If these steps don't resolve your issue, I recommend opening a new issue in the [Airbyte Github repository](https://github.com/airbytehq/airbyte/issues) detailing your problem. Include as much information as possible, such as the connector version, your configuration, and any relevant log outputs. This will help the Airbyte team diagnose and potentially fix your issue.

@Simón Echeverri were you able to find a solution?

Hey running into the same issue, did anyone here find a solution?