github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 03:32:54 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Bug]: "There was an internal error" when syncing a specific account #1666

New Issue
Closed
opened 2026-02-28 19:50:25 -06:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-02-28 19:50:25 -06:00
Owner
Copy Link

Originally created by @Arnoud-B on GitHub (Dec 12, 2024).

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?

For over a month now I get a "There was an internal error" message when syncing a specific account. Even when I recreate the account + sync, I still get the error. Is this a GoCardless issue or an Actual Budget issue?

Exact error message:
CleanShot 2024-12-12 at 10 18 18@2x

Console logs:
CleanShot 2024-12-12 at 10 16 37@2x
CleanShot 2024-12-12 at 10 18 51@2x

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Firefox, Safari

Operating System

Mac OSX

Originally created by @Arnoud-B on GitHub (Dec 12, 2024). ### Verified issue does not already exist? - [X] I have searched and found no existing issue - [X] I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file) ### What happened? For over a month now I get a "There was an internal error" message when syncing a specific account. Even when I recreate the account + sync, I still get the error. Is this a GoCardless issue or an Actual Budget issue? Exact error message: ![CleanShot 2024-12-12 at 10 18 18@2x](https://github.com/user-attachments/assets/9fc296ee-5e0b-400f-b36f-292abb4cd60d) Console logs: ![CleanShot 2024-12-12 at 10 16 37@2x](https://github.com/user-attachments/assets/f6a08927-959d-4497-b97b-cf31f6f66947) ![CleanShot 2024-12-12 at 10 18 51@2x](https://github.com/user-attachments/assets/4afec1c7-2455-428e-9610-d37b2945b456) ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Firefox, Safari ### Operating System Mac OSX
GiteaMirror added the bug label 2026-02-28 19:50:25 -06:00
GiteaMirror commented 2026-02-28 19:50:26 -06:00
Author
Owner
Copy Link

@MMichotte commented on GitHub (Dec 24, 2024):

Same issue here but slightly different error message:
Screenshot 2024-12-24 at 12 08 25

@MMichotte commented on GitHub (Dec 24, 2024): Same issue here but slightly different error message: <img width="411" alt="Screenshot 2024-12-24 at 12 08 25" src="https://github.com/user-attachments/assets/c0c6c919-2cee-4866-bcf4-88df4edba078" />
GiteaMirror commented 2026-02-28 19:50:27 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Dec 24, 2024):

If you have not reached out on discord for this already please do. We try to keep all bank sync support over there. Ill close this for now, but if you are able to track down a specific bug then you can reopen this or open a new ticket.

@youngcw commented on GitHub (Dec 24, 2024): If you have not reached out on discord for this already please do. We try to keep all bank sync support over there. Ill close this for now, but if you are able to track down a specific bug then you can reopen this or open a new ticket.
GiteaMirror commented 2026-02-28 19:50:27 -06:00
Author
Owner
Copy Link

@Arnoud-B commented on GitHub (Dec 27, 2024):

@MMichotte Thanks for sharing your error log as well. I noticed something different in there that I suspected was related to my issue as well:
Error: payeeName is required
I remembered I have a recurring transaction set up with a schedule where the payee name is automatically removed each time for some reason. So I searched for this transaction, updated the payee name so it wouldn't be empty, and voila: the error did not occur again!

@youngcw I hadn't reached out on Discord because it seemed I needed an invitation first.

@Arnoud-B commented on GitHub (Dec 27, 2024): @MMichotte Thanks for sharing your error log as well. I noticed something different in there that I suspected was related to my issue as well: `Error: payeeName is required` I remembered I have a recurring transaction set up with a schedule where the payee name is automatically removed each time for some reason. So I searched for this transaction, updated the payee name so it wouldn't be empty, and voila: the error did not occur again! @youngcw I hadn't reached out on Discord because it seemed I needed an invitation first.
GiteaMirror commented 2026-02-28 19:50:27 -06:00
Author
Owner
Copy Link

@MMichotte commented on GitHub (Dec 30, 2024):

I found the culprit in my case.
One transaction does indeed not contain a payeeName. The issue is that it directly comes like that from my bank so I have no way of changing that.

If I recall correctly, it originated from a generated multi-QR code to quickly be reimbursed by multiple friends. Other one-to-one QR codes seem to work properly though.

{
    "transactionId": "2024-12-09-08.38.45.738194",
    "bookingDate": "2024-12-09",
    "valueDate": "2024-12-09",
    "transactionAmount": {
        "amount": "9.00",
        "currency": "EUR"
    },
    "creditorName": "XXXXX MARTIN",
    "creditorAccount": {
        "iban": "BE0000000005970",
        "currency": "EUR"
    },
    "remittanceInformationStructured": "66640124341147062103XXXXXX680341140",
    "bankTransactionCode": "PMNT-MCRD-POSP",
    "proprietaryBankTransactionCode": "0450000",
    "internalTransactionId": "356c753577b9683b24d211f1fe4676f0",
    "date": "2024-12-09",
    "booked": true
}
Screenshot 2024-12-30 at 14 12 46

I am not sure on how this could be solved at its root so maybe we should handle this exception in the goCardless connector ?
Adding an "unknown" payeeName by default (or blank "" ?) for example ?
@youngcw what do you think about this ?

@MMichotte commented on GitHub (Dec 30, 2024): I found the culprit in my case. One transaction does indeed not contain a payeeName. The issue is that it directly comes like that from my bank so I have no way of changing that. If I recall correctly, it originated from a generated multi-QR code to quickly be reimbursed by multiple friends. Other one-to-one QR codes seem to work properly though. ```json { "transactionId": "2024-12-09-08.38.45.738194", "bookingDate": "2024-12-09", "valueDate": "2024-12-09", "transactionAmount": { "amount": "9.00", "currency": "EUR" }, "creditorName": "XXXXX MARTIN", "creditorAccount": { "iban": "BE0000000005970", "currency": "EUR" }, "remittanceInformationStructured": "66640124341147062103XXXXXX680341140", "bankTransactionCode": "PMNT-MCRD-POSP", "proprietaryBankTransactionCode": "0450000", "internalTransactionId": "356c753577b9683b24d211f1fe4676f0", "date": "2024-12-09", "booked": true } ``` <img width="1176" alt="Screenshot 2024-12-30 at 14 12 46" src="https://github.com/user-attachments/assets/ff786bd3-76b1-43a0-b5a7-c4059a51eafd" /> I am not sure on how this could be solved at its root so maybe we should handle this exception in the goCardless connector ? Adding an "unknown" payeeName by default (or blank "" ?) for example ? @youngcw what do you think about this ?
GiteaMirror commented 2026-02-28 19:50:28 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Dec 30, 2024):

@MMichotte you should open a new issue for that

@youngcw commented on GitHub (Dec 30, 2024): @MMichotte you should open a new issue for that
GiteaMirror commented 2026-02-28 19:50:28 -06:00
Author
Owner
Copy Link

@robxgd commented on GitHub (Jan 3, 2025):

@MMichotte I am having the same issue. logged the official issue here: https://github.com/actualbudget/actual-server/issues/532

@robxgd commented on GitHub (Jan 3, 2025): @MMichotte I am having the same issue. logged the official issue here: https://github.com/actualbudget/actual-server/issues/532
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#1666
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?