[Bug]: No way of knowing when rate limit will be lifted #488
Labels
bug
Something isn't working
Comments
|
I was thinking about the same problem. It could be that there are two rate limits to consider - one imposed by GoCardless, and the other one imposed by the bank. I suspect we could be hitting the latter (the bank rate limit), and not the former. |
|
It may be a good idea to start logging it for now and dealing with the UI
later
Best regards,
Zemfira
…On Thu, Oct 31, 2024, 7:56 PM mbrijun ***@***.***> wrote:
I was thinking about the same problem. It could be that there are two rate
limits to consider - one imposed by GoCardless, and the other one imposed
by the bank. I suspect we could be hitting the latter (the bank rate
limit), and not the former.
—
Reply to this email directly, view it on GitHub
<#488 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJNTN6ZTYXTXB2W7MLPORRLZ6J4MHAVCNFSM6AAAAABQZG6PL2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJQGYYDSOBUHA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Verified issue does not already exist?
What happened?
There is no way of knowing when the rate limit is gonna be lifted again when using gocardless
Should be a relatively easy fix to add the actual error from gocardless here
actual-server/src/app-gocardless/app-gocardless.js
Line 226 in 603f970
They claim to return it in their API spec
https://developer.gocardless.com/bank-account-data/endpoints
{ "summary": "Rate limit exceeded", "detail": "The rate limit for this resource is <times>/<time_period>. Please try again in <time_left> seconds", "status_code": 429 }Logs do not report anything useful with
DEBUG="*"What error did you receive?
No response
Where are you hosting Actual?
Other
What browsers are you seeing the problem on?
No response
Operating System
Linux
The text was updated successfully, but these errors were encountered: