Hello guys. Anyone had this problem with Recurly source? It keeps stuck at this point and takes too long (1h25min) to pass from this step to the normalization step. I'm trying to get invoices and transactions.

Maybe your scheduler reach the maximum parallel connections allow and took 1h to finish another process and start normalization. Check your

.env

variables and follow the

docker ps

containers number

Great! I checked it but we just have only three processes. They rarely work in parallel and this problem occours only when we trigger the Recurly job. It seems to get stucked always in the same step and when it passes this step the normalization step goes fast (about 3 minutes)

Hi Victor! I'm looking into this for you, but will be off for the rest of the week. Hope you enjoy the Thanksgiving celebrations as well and I hope to have some ideas for you early next week!

Thank you Nataly! It will be really helpful to me.

Could you provide the full logs? Usually in the full logs you can see the sync happening row by row and if it's hitting any rate limits or anything 🤔 are you syncing a lot of data? What is the deployment environment?

We are working with the Digital Ocean droplet. These are it's specifications:

Thank you, looking forward to it!

Here is the logs for my recurly airbyte connection. It processes 1.7 GB again even with the incremental input set

One thing I noticed in your logs is the Airbyte version:

Airbyte version: 0.30.25-alpha

Could you please update to the most recent version? This might be causing issues in your connection.

Great!! I'll check that

So glad to hear that!