Hey Meltano team! Is anyone using tap-recharge within Meltano? We're regularly bumping up against rate limits We've tried • Reducing calls per minute to 90 • Adding 5 second delay to the calls • Drastically reducing target batch size (not ideal) • Using a new access token

https://github.com/singer-io/tap-recharge/pull/24 is this the PR you are talking about? Looks like they put some back off in for this one

@visch we implemented these changes in a repo that we own, and we're still facing some 429 errors. It's a head scratcher for sure

I don't have a fix for you but here's what's on my brain 1. Is the tap actually only doing the number of requests you expect? To find out if that's true or not you could turn on requests logging and then make some kind of script to count the number of requests that are happening over some time frame. (Could also be a decent use case for https://vcrpy.readthedocs.io/en/latest/ , @florian.hines pointed to this a while back I think) 2. If you verify #1 is correct then I'd send a support ticket over to the recharge folks (I'd probably start with this anyway as it's low effort, and just ask about the issue as who knows what their team knows about this issue, they may have a fix for you)

@visch thanks for these suggestions! I'll let you know how it turns out