Report passes without any data after connector upgrade

  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Ubuntu
  • Memory / Disk: 100 GB
  • Deployment: Docker
  • Airbyte Version: 0.40.27
  • Source name/version: Amazon Selling Partner v. 0.2.31
  • Destination name/version: MySQL v. 0.1.20
  • Step: The issue is happening during sync
  • Description:
    I updated the connectors to the newest version and tried to sync the report ‘GET_FLAT_FILE_ALL_ORDERS_DATA_BY_LAST_UPDATE_GENERAL’ but the sync passes after a minute or two without any data beeing synced:

7ec40cb4_5316_4ebc_9fd9_96e2e7dc4af9_logs_20_txt.txt (29.5 KB)

With an earlier version this report will response with a file of over 6gb data but i cant use this since refreshing the access token is not supported in earlier versions.

Could this happen because im still on Airbyte version 0.40.27?
Sadly i cant upgrade to 0.40.30 yet (reference this thread)

EDIT: I tried it with a clean install on version 0.40.30 but the issue stays

Since its a fresh installation this seems like a bug in the asp connector, i opened an issue on github:

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
The Community Assistance Team

Created issue in Github