github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 20:15:33 -05:00
Code Issues 1.5k Packages Projects Releases 55 Wiki Activity

[Bug]: (v23.12.0) N26 with multiple spaces sync through GoCardless gives "something internally went wrong" #810

New Issue
Closed
opened 2026-02-28 19:20:41 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-02-28 19:20:41 -06:00
Owner
Copy Link

Originally created by @Arnoud-B on GitHub (Dec 11, 2023).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

I have an N26 account with multiple spaces. When I set it up a few weeks ago with sync via GoCardless I ran into the "something internally went wrong" issue, but I don't think it appeared on every sync in the past weeks. Today it appeared again, and it seemed to be related to a transfer between a space and the main account because the transfer showed up twice in the space (transfer out and transfer in of the same amount, while it should only have been a transfer out).

So I unlinked all three accounts (main account + 2 spaces), I force closed the 2 spaces and recreated them, then linked everything up again through GoCardless. Then I received the "something internally went wrong" message 3 times in a row (see screenshot).

The data looks alright, but the transfers between the spaces and the main account are not recognized as transfers. When I tell Actual that it's a transfer, I get duplicates.

Now, a sync on the spaces gives no error, but a sync on the main account does still give the same error.

What error did you receive?

Screenshot 2023-12-11 at 13 06 40 (Actual)@2x

Where are you hosting Actual?

Locally via Yarn

What browsers are you seeing the problem on?

Safari

Operating System

Mac OSX

Originally created by @Arnoud-B on GitHub (Dec 11, 2023). ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? I have an N26 account with multiple spaces. When I set it up a few weeks ago with sync via GoCardless I ran into the "something internally went wrong" issue, but I don't think it appeared on every sync in the past weeks. Today it appeared again, and it seemed to be related to a transfer between a space and the main account because the transfer showed up twice in the space (transfer out and transfer in of the same amount, while it should only have been a transfer out). So I unlinked all three accounts (main account + 2 spaces), I force closed the 2 spaces and recreated them, then linked everything up again through GoCardless. Then I received the "something internally went wrong" message 3 times in a row (see screenshot). The data looks alright, but the transfers between the spaces and the main account are not recognized as transfers. When I tell Actual that it's a transfer, I get duplicates. Now, a sync on the spaces gives no error, but a sync on the main account does still give the same error. ### What error did you receive? ![Screenshot 2023-12-11 at 13 06 40 (Actual)@2x](https://github.com/actualbudget/actual/assets/11488458/ac67b312-1481-451a-8582-d6cb2f6a352c) ### Where are you hosting Actual? Locally via Yarn ### What browsers are you seeing the problem on? Safari ### Operating System Mac OSX
GiteaMirror added the bug label 2026-02-28 19:20:41 -06:00
GiteaMirror commented 2026-02-28 19:20:42 -06:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Dec 30, 2023):

👋 I have N26 and have not observed any issues so far.

Do you have the server logs for the internal error you're experiencing?

@MatissJanis commented on GitHub (Dec 30, 2023): 👋 I have N26 and have not observed any issues so far. Do you have the server logs for the internal error you're experiencing?
GiteaMirror commented 2026-02-28 19:20:42 -06:00
Author
Owner
Copy Link

@xocasdashdash commented on GitHub (Jan 5, 2024):

@MatissJanis I'm seeing an error too but mine says:

Something went wrong {
  summary: "Couldn't update account transactions",
  detail: 'Access has expired or it has been revoked. To restore access reconnect the account.',
  status_code: 401,
  type: 'AccessExpiredError'
}

Right after i link the account in N26 website

@xocasdashdash commented on GitHub (Jan 5, 2024): @MatissJanis I'm seeing an error too but mine says: ``` Something went wrong { summary: "Couldn't update account transactions", detail: 'Access has expired or it has been revoked. To restore access reconnect the account.', status_code: 401, type: 'AccessExpiredError' } ``` Right after i link the account in N26 website
GiteaMirror commented 2026-02-28 19:20:43 -06:00
Author
Owner
Copy Link

@xocasdashdash commented on GitHub (Jan 8, 2024):

I pinged gocardless and there's something wrong on N26 side and they're going to be reaching out to them.

@xocasdashdash commented on GitHub (Jan 8, 2024): I pinged gocardless and there's something wrong on N26 side and they're going to be reaching out to them.
GiteaMirror commented 2026-02-28 19:20:43 -06:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Jan 8, 2024):

Great. Yes, this does seem to be on their end, so I'll close the issue.

@MatissJanis commented on GitHub (Jan 8, 2024): Great. Yes, this does seem to be on their end, so I'll close the issue.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#810
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?