API failures with TTransportException

[kv testing 0]

Hello Evernote Community,

I’m using the Evernote Java client library to interact with the Evernote APIs, and I’ve been encountering frequent API failures with the following error:

com.evernote.thrift.transport.TTransportException: HTTP Response code: 429

As many of you may know, HTTP error code 429 corresponds to "Too Many Requests." However, rate limit exceptions are typically handled by EDAMException, which includes the rate limit duration. Despite this, I’m still experiencing the 429 errors, and the rate limits don't seem to be properly managed.

I have reported the issue many times to Evernote devloper support team and there is no proper response from them. I’m wondering if anyone else is facing the same problem. Could it be that there’s a bug on Evernote's side causing these repeated failures?

Any guidance or insights would be greatly appreciated!

[PinkElephant 9,015]

Only a few devs here, and most not frequently.

You better contact support.