[PR #4993] [CLOSED] Fix/gocardless rate limit select accounts #5694

Closed
opened 2026-02-28 21:16:52 -06:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/actualbudget/actual/pull/4993
Author: @lorenzenv
Created: 5/15/2025
Status: Closed

Base: masterHead: fix/gocardless-rate-limit-select-accounts


📝 Commits (2)

  • beb6759 Enable server-side account selection for linking
  • 505ef95 docs: Add release note for GoCardless rate limit fix

📊 Changes

2 files changed (+7 additions, -1 deletions)

View changed files

📝 packages/sync-server/src/app-gocardless/services/gocardless-service.js (+1 -1)
upcoming-release-notes/4993.md (+6 -0)

📄 Description

Problem:

Users attempting to link bank accounts via GoCardless frequently encounter "Daily request limit set by the Institution has been exceeded" errors (as reported in issue #4039). This error prevents successful account linking and occurs because the previous integration attempted to fetch details for all of an institution's accounts upfront.

Solution:

This PR fixes the issue by modifying the GoCardless integration (packages/sync-server/src/app-gocardless/services/gocardless-service.js) to enable server-side account selection provided by GoCardless.

The accountSelection parameter in the client.initSession call (within the createRequisition function) has been changed from false to true.

Impact:

  • When a user initiates a new bank link with GoCardless, they will now be redirected to the GoCardless platform, which should prompt them to select the specific account(s) they wish to grant Actual access to.
  • Actual's backend will then only receive the IDs for these pre-selected accounts in the requisition.
  • This drastically reduces the number of subsequent API calls Actual needs to make, effectively resolving the institutional rate limit errors during the account discovery phase.
  • This leads to a more reliable bank linking experience for GoCardless users affected by these limits.

Testing:

  1. Set up GoCardless credentials in Actual.
  2. Attempt to add a new linked account using GoCardless with an institution previously causing rate limit errors.
  3. Observe that during the redirection to GoCardless, an account selection step is presented.
  4. Select one or more accounts.
  5. Upon redirection back to Actual, verify that only the selected accounts are listed and can be linked successfully without rate limit errors.

Closes #4039


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/actualbudget/actual/pull/4993 **Author:** [@lorenzenv](https://github.com/lorenzenv) **Created:** 5/15/2025 **Status:** ❌ Closed **Base:** `master` ← **Head:** `fix/gocardless-rate-limit-select-accounts` --- ### 📝 Commits (2) - [`beb6759`](https://github.com/actualbudget/actual/commit/beb6759b246cc6abd3db731c93dd2316cd74c156) Enable server-side account selection for linking - [`505ef95`](https://github.com/actualbudget/actual/commit/505ef951f076e6d621c6c7e955cd9ac093469395) docs: Add release note for GoCardless rate limit fix ### 📊 Changes **2 files changed** (+7 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `packages/sync-server/src/app-gocardless/services/gocardless-service.js` (+1 -1) ➕ `upcoming-release-notes/4993.md` (+6 -0) </details> ### 📄 Description **Problem:** Users attempting to link bank accounts via GoCardless frequently encounter "Daily request limit set by the Institution has been exceeded" errors (as reported in issue #4039). This error prevents successful account linking and occurs because the previous integration attempted to fetch details for all of an institution's accounts upfront. **Solution:** This PR fixes the issue by modifying the GoCardless integration (`packages/sync-server/src/app-gocardless/services/gocardless-service.js`) to enable server-side account selection provided by GoCardless. The `accountSelection` parameter in the `client.initSession` call (within the `createRequisition` function) has been changed from `false` to `true`. **Impact:** - When a user initiates a new bank link with GoCardless, they will now be redirected to the GoCardless platform, which should prompt them to select the specific account(s) they wish to grant Actual access to. - Actual's backend will then only receive the IDs for these pre-selected accounts in the requisition. - This drastically reduces the number of subsequent API calls Actual needs to make, effectively resolving the institutional rate limit errors during the account discovery phase. - This leads to a more reliable bank linking experience for GoCardless users affected by these limits. **Testing:** 1. Set up GoCardless credentials in Actual. 2. Attempt to add a new linked account using GoCardless with an institution previously causing rate limit errors. 3. Observe that during the redirection to GoCardless, an account selection step is presented. 4. Select one or more accounts. 5. Upon redirection back to Actual, verify that only the selected accounts are listed and can be linked successfully without rate limit errors. Closes #4039 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-02-28 21:16:52 -06:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#5694