Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: No way of knowing when rate limit will be lifted #488

Open
1 task done
fira42073 opened this issue Oct 29, 2024 · 2 comments
Open
1 task done

[Bug]: No way of knowing when rate limit will be lifted #488

fira42073 opened this issue Oct 29, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@fira42073
Copy link

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

There is no way of knowing when the rate limit is gonna be lifted again when using gocardless

image

Should be a relatively easy fix to add the actual error from gocardless here

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="*"
image

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

@mbrijun
Copy link

mbrijun commented Oct 31, 2024

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.

@fira42073
Copy link
Author

fira42073 commented Oct 31, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants