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]: Bank-Sync Rate Limit error handling #3120

Closed
2 tasks done
xrebelox opened this issue Jul 22, 2024 · 5 comments
Closed
2 tasks done

[Bug]: Bank-Sync Rate Limit error handling #3120

xrebelox opened this issue Jul 22, 2024 · 5 comments
Labels
bank sync Related to automatic bank syncing bug Something isn't working

Comments

@xrebelox
Copy link

Verified issue does not already exist?

  • I have searched and found no existing issue
  • I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file)

What happened?

It seems some institutions set a daily rate limit which is fine, however, Actual provides a generic error This account is experiencing connection problems. Let's fix it. when you click to check said error it just shows like this:
image

Checking the docker logs I can see that the error is as follows:

{
  summary: "Couldn't update account transactions",
  detail: 'Daily request limit set by the Institution has been exceeded.',
  status_code: 429,
  type: 'RateLimitError'
}

I looked into the code and we're already handling the RateLimitError but it seems that the error sent to the front-end is not correct (I checked the network requests and the error was sent when hitting the /gocardless/transactions), here's the response from the API:

{
    "status": "ok",
    "data": {
        "error_type": "SYNC_ERROR",
        "error_code": "NORDIGEN_ERROR"
    }
}

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome

Operating System

Linux

@xrebelox xrebelox added the bug Something isn't working label Jul 22, 2024
@youngcw youngcw added the bank sync Related to automatic bank syncing label Jul 26, 2024
@totalitarian
Copy link

Same issue

@denkristoffer
Copy link

It would be nice if this was handled better because GoCardless has begun to heavily rate limit:

Starting from 19 August 2024, we will implement a limit of 10 API requests per day for each access scope (details, balances, transactions) on account id level as part of our ongoing efforts to enhance operational effectiveness and minimize potential issues for all our clients. This phased approach will allow us to optimize our services progressively.

We plan to establish a limit of four requests per day for each access scope in the next phase.

From an email they sent out a couple of weeks ago. I still don't see this limit being mentioned in their docs.

@totalitarian
Copy link

It would be nice if this was handled better because GoCardless has begun to heavily rate limit:

Starting from 19 August 2024, we will implement a limit of 10 API requests per day for each access scope (details, balances, transactions) on account id level as part of our ongoing efforts to enhance operational effectiveness and minimize potential issues for all our clients. This phased approach will allow us to optimize our services progressively.
We plan to establish a limit of four requests per day for each access scope in the next phase.

From an email they sent out a couple of weeks ago. I still don't see this limit being mentioned in their docs.

Damn, 4 per day is going to hurt

@matt-fidd
Copy link
Contributor

This should be fixed in latest as long as you're running the most recent server and front end.

image

image

actualbudget/actual-server#439

@matt-fidd
Copy link
Contributor

There's an issue tracking this actualbudget/actual-server#431

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

No branches or pull requests

5 participants