actual: [Bug]: White screen after clicking "Continue" after setting up account linking with GoCardless
Verified issue does not already exist?
- I have searched and found no existing issue
What happened?
I repeatedly tried to set up my bank account syncing via GoCardless. I exceeded a limit by my institution while doing this, apparently –
(in the JS console, network tab, I can see a request to https://precise-dragon.pikapod.net/gocardless/get-accounts while setting up sync returned:)
{
"status": "ok",
"data": {
"error_code": "INTERNAL_ERROR",
"error_type": "Daily request limit set by the Institution has been exceeded"
}
}
But this error doesn’t make it to the UI. Instead, the UI says the setup went fine and if I click the ‘continue’ button I can set up which accounts get synced - but if I do that, I get a white screen.
The JS console error then is
Uncaught TypeError: Cannot read properties of undefined (reading 'sort')
at this line:
externalAccounts.sort((a, b) => a.name.localeCompare(b.name));
in SelectLinkedAccountsModal.jsx:34.
I can see that GoCardless (by listing requisitions using the API) has successfully authorised the account by something has clearly fallen over in the process.
How can we reproduce the issue?
- Click ‘add account’ on sidebar
- Choose to link using GoCardless
- Go through GoCardless registration setup
- Get back to Actual, wait for “waiting for GoCardless…” to disappear and the Continue button to appear
- Click the Continue button
Where are you hosting Actual?
Pikapods
What browsers are you seeing the problem on?
Chrome, Safari
Operating System
Mac OSX
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 11
- Comments: 17 (2 by maintainers)
I tried using other apps (Spendee / Bankin) and they connect just fine also using psd2 so I’m pretty sure this rate limit is coming from GoCardless.
That being said, I wonder if a solution could be to not fetch the details of account that are already closed. I think that’s the reason why it fails
I updated Actual to v25.4.0, but it didn’t help for me.
I think i’ve found why the
Daily request limit set by the Institution has been exceeded. A long time ago, I’ve created multiple spaces in N26 to make some tests, and then deleted it, but GoCardLess still find them. The result is that now I have 22 entries in GoCardLess for my N26 account.When Actual encounters the Daily limit error, the logs show that Actual was trying to reach every entries, and it seems that it was trying to contact them multiple times. So in my case it creates more than 30 request to N26, and it triggers the daily limit.
EDIT: When recreating any request that was in the log with this curl request:
I have a good 200 response, that contains:
But after multiple requests, I finally have this error message:
So it seems to be a limit of 4 request per account ID per day (the id that is REDACTED above). I did’nt managed to find an account id that is already blocked, every account id I’ve tried was only reached 1 time. So I don’t know the exact request that triggered the 429 error with Actual.
Here is some related GoCardLess doc.
I experience the same problem with my N26 accounts from the very beginning. It has not ever worked on several attempts several days.
The log in the console upon successfully linking the accounts from GoCardless Open Banking API;
I too have a similar error, I see this in the log:
It would be nice if the UI exposed the error to the user instead of swallowing the error and just showing a white screen
I installed v25.4.0 immediately once I saw it available, as I had the impression that it’d have improved the experience around this issue. It indeed did. Now, instead of seeing a white screen, I see an empty accounts dialog, as can be seen in the screenshot below.
I am trying to connect my N26 account every 2-3 days to safely dodge rate limits per day. However, whenever I try, it immediately hits rate limits as below.
POST https://redacted-host.tld/gocardless/get-accounts
Same problem here. (running Actual with docker) I also have
Daily request limit set by the Institution has been exceededAnd after clicking the continue button, the browser console also shows:
The daily limit is not an error from Actual, but it would be better to print a pretty error message in the UI + preventing from clicking the continue button, instead of failing silently.
Without doing anything (nothing but waiting 3 days), https://github.com/actualbudget/actual/issues/3888#issuecomment-2507944242 that was facing a similar issue managed to connect Actual to N26.
More container logs here:
Hey folks, I managed to get this working. The key was to change the GoCardless integration to use
accountSelection: truewhen creating the requisition; this way, GoCardless handles the account selection upfront on their end. Then Actual’s backend only has to fetch details for the accounts I specifically chose, which avoids hitting the bank’s rate limits by not trying to process all accounts initially…