Hi, I created the above mentioned connection and it is expected that the sync will fail but usually when syncs failed it triggered 2nd & 3rd attempt automatically.
But now its staying in retrying state and no 2nd or 3rd attempt is triggered.
Can we please look into this issue, as it once goes to retrying/incomplete state, user becomes trigger a 2nd job for it.
In below attached image, we can observe following 3 things:
-Sync was triggered at 1:30pm & current time is 1:44pm, it means the sync is in retrying state for 15 mins.
-We can observe that there is only 1 attempt even though it says retrying.
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.
Best,
The Community Assistance Team
Thanks for the post and apologies for the significant delay in response.
Since it’s been a number of days since you first made your post, can you upgrade to the latest versions of Airbyte and the Mailchimp and Redshift connectors? There are have been significant changes to our platform, which may solve the issues you’re facing.
Please report back with your experience after upgrading and let me know if the issues are still persisting. I’ll be happy to escalate it to Github where our team will determine if it’s the cause of a bug. Thanks for using Airbyte and apologies for the delay in response.
