[Bug]: Syncing Monzo bank via GoCardless #2281

Closed
opened 2026-02-28 20:08:52 -06:00 by GiteaMirror · 1 comment
Owner

Originally created by @jaskaransarkaria on GitHub (Jul 14, 2025).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

After I have linked the account I then attempt a sync and receive the following error (note syncing other banks eg.Starling works great):

Environment:

UK based bank accounts
self hosted server in Kubernetes : v25.7.1
desktop app version: v25.7.1

Desktop Error (adding for context):

"Server Log: [Exception] {\n  type: 'BankSyncError',\n  category: 'UNKNOWN',\n  code: 'UNKNOWN',\n  details: {\n    rateLimitHeaders: {\n      http_x_ratelimit_limit: '100',\n      http_x_ratelimit_remaining: '99',\n      http_x_ratelimit_reset: '59',\n      http_x_ratelimit_account_success_limit: '4',\n      http_x_ratelimit_account_success_remaining: '4',\n      http_x_ratelimit_account_success_reset: '86400'\n    }\n  }\n}"
"Server Log: node:internal/process/promises:389\n      new UnhandledPromiseRejection(reason);\n      ^\n\nUnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason \"#<Object>\".\n    at throwUnhandledRejectionsMode (node:internal/process/promises:389:7)\n    at processPromiseRejections (node:internal/process/promises:470:17)\n    at process.processTicksAndRejections (node:internal/process/task_queues:96:32) {\n  code: 'ERR_UNHANDLED_REJECTION'\n}\n\nNode.js v20.16.0"

On the server the error is a 503:

Something went wrong ServiceError: Institution service unavailable
    at handleGoCardlessError (file:///app/src/app-gocardless/services/gocardless-service.js:38:19)
    at Object.getTransactions (file:///app/src/app-gocardless/services/gocardless-service.js:458:13)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Object.getNormalizedTransactions (file:///app/src/app-gocardless/services/gocardless-service.js:196:30)
    at async file:///app/src/app-gocardless/app-gocardless.js:123:80 {
  details: h [AxiosError]: Request failed with status code 503
      at te (file:///app/node_modules/nordigen-node/dist/index.esm.js:13:914)
      at IncomingMessage.<anonymous> (file:///app/node_modules/nordigen-node/dist/index.esm.js:17:16315)
      at IncomingMessage.emit (node:events:536:35)
      at endReadableNT (node:internal/streams/readable:1698:12)
      at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
    code: 'ERR_BAD_RESPONSE',

more server response details:

response: {
  status: 503,
  statusText: 'Service Unavailable',
  headers: T [AxiosHeaders] {
    date: 'Mon, 14 Jul 2025 20:36:04 GMT',
    'content-type': 'application/json',
    'content-length': '136',
    connection: 'keep-alive',
    vary: 'Accept, Accept-Language, Cookie, Accept-Encoding',
    allow: 'GET, HEAD, OPTIONS',
    http_x_ratelimit_limit: '100',
    http_x_ratelimit_remaining: '99',
    http_x_ratelimit_reset: '59',
    http_x_ratelimit_account_success_limit: '4',
    http_x_ratelimit_account_success_remaining: '4',
    http_x_ratelimit_account_success_reset: '86400',
    'cache-control': 'no-store, no-cache, max-age=0',
    'x-c-uuid': 'xxxxxxxxxxxxxxxxxxxxxxxxxxxx',
    'x-u-uuid': 'xxxxxxxxxxxxxxxxxxxxxxxxxxxx',
    'x-frame-options': 'DENY',
    'content-language': 'en',
    'x-content-type-options': 'nosniff',
    'referrer-policy': 'same-origin',
    'client-region': 'NL',
    'cf-ipcountry': 'GB',
    'strict-transport-security': 'max-age=31556926; includeSubDomains;',
    'cf-cache-status': 'BYPASS',
...
      data: {
        summary: "Couldn't update account transactions",
        detail: "Couldn't connect to Institution",
        status_code: 503,
        type: 'ConnectionError'
      }
    }
  }
}

How can we reproduce the issue?

How can we reproduce the issue?

When attempting to sync a newly created linked account with GoCardless using UK bank Monzo.

Where are you hosting Actual?

Other

What browsers are you seeing the problem on?

Desktop App (Electron)

Operating System

Linux

Originally created by @jaskaransarkaria on GitHub (Jul 14, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? After I have linked the account I then attempt a sync and receive the following error (note syncing other banks eg.Starling works great): Environment: ``` UK based bank accounts self hosted server in Kubernetes : v25.7.1 desktop app version: v25.7.1 ``` Desktop Error (adding for context): ``` "Server Log: [Exception] {\n type: 'BankSyncError',\n category: 'UNKNOWN',\n code: 'UNKNOWN',\n details: {\n rateLimitHeaders: {\n http_x_ratelimit_limit: '100',\n http_x_ratelimit_remaining: '99',\n http_x_ratelimit_reset: '59',\n http_x_ratelimit_account_success_limit: '4',\n http_x_ratelimit_account_success_remaining: '4',\n http_x_ratelimit_account_success_reset: '86400'\n }\n }\n}" "Server Log: node:internal/process/promises:389\n new UnhandledPromiseRejection(reason);\n ^\n\nUnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason \"#<Object>\".\n at throwUnhandledRejectionsMode (node:internal/process/promises:389:7)\n at processPromiseRejections (node:internal/process/promises:470:17)\n at process.processTicksAndRejections (node:internal/process/task_queues:96:32) {\n code: 'ERR_UNHANDLED_REJECTION'\n}\n\nNode.js v20.16.0" ``` On the server the error is a 503: ``` Something went wrong ServiceError: Institution service unavailable at handleGoCardlessError (file:///app/src/app-gocardless/services/gocardless-service.js:38:19) at Object.getTransactions (file:///app/src/app-gocardless/services/gocardless-service.js:458:13) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Object.getNormalizedTransactions (file:///app/src/app-gocardless/services/gocardless-service.js:196:30) at async file:///app/src/app-gocardless/app-gocardless.js:123:80 { details: h [AxiosError]: Request failed with status code 503 at te (file:///app/node_modules/nordigen-node/dist/index.esm.js:13:914) at IncomingMessage.<anonymous> (file:///app/node_modules/nordigen-node/dist/index.esm.js:17:16315) at IncomingMessage.emit (node:events:536:35) at endReadableNT (node:internal/streams/readable:1698:12) at process.processTicksAndRejections (node:internal/process/task_queues:82:21) { code: 'ERR_BAD_RESPONSE', ``` more server response details: ``` response: { status: 503, statusText: 'Service Unavailable', headers: T [AxiosHeaders] { date: 'Mon, 14 Jul 2025 20:36:04 GMT', 'content-type': 'application/json', 'content-length': '136', connection: 'keep-alive', vary: 'Accept, Accept-Language, Cookie, Accept-Encoding', allow: 'GET, HEAD, OPTIONS', http_x_ratelimit_limit: '100', http_x_ratelimit_remaining: '99', http_x_ratelimit_reset: '59', http_x_ratelimit_account_success_limit: '4', http_x_ratelimit_account_success_remaining: '4', http_x_ratelimit_account_success_reset: '86400', 'cache-control': 'no-store, no-cache, max-age=0', 'x-c-uuid': 'xxxxxxxxxxxxxxxxxxxxxxxxxxxx', 'x-u-uuid': 'xxxxxxxxxxxxxxxxxxxxxxxxxxxx', 'x-frame-options': 'DENY', 'content-language': 'en', 'x-content-type-options': 'nosniff', 'referrer-policy': 'same-origin', 'client-region': 'NL', 'cf-ipcountry': 'GB', 'strict-transport-security': 'max-age=31556926; includeSubDomains;', 'cf-cache-status': 'BYPASS', ... data: { summary: "Couldn't update account transactions", detail: "Couldn't connect to Institution", status_code: 503, type: 'ConnectionError' } } } } ``` ### How can we reproduce the issue? How can we reproduce the issue? When attempting to sync a newly created linked account with GoCardless using UK bank Monzo. ### Where are you hosting Actual? Other ### What browsers are you seeing the problem on? Desktop App (Electron) ### Operating System Linux
GiteaMirror added the bug label 2026-02-28 20:08:52 -06:00
Author
Owner

@youngcw commented on GitHub (Jul 14, 2025):

Please reach out on discord for tech support.

@youngcw commented on GitHub (Jul 14, 2025): Please reach out on discord for tech support.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#2281