github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-16 07:04:23 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[Bug]: Fatal Error - There was an unrecoverable error in the UI. Sorry! #1849

New Issue
Closed
opened 2026-02-28 19:56:16 -06:00 by GiteaMirror · 11 comments
GiteaMirror commented 2026-02-28 19:56:16 -06:00
Owner
Copy Link

Originally created by @zenmeow88 on GitHub (Feb 10, 2025).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

I'm currently running v25.2.1 on Chrome browser on Windows 11 desktop.

Clicked on "Expand/Collapse split transaction" button on top right after deleted an existing split transactions, the error message below pop up. "Reset budget cache" and "Repair transaction" in the setting did not help, I had to use mobile (Android) to recreate the split or delete the "parent" transaction to resolve the issue.

Unable to access to the following 3 pages after the error appeared:

  1. All accounts
  2. On budget
  3. Specific account where the split transaction occured

Error Message:

Fatal Error
There was an unrecoverable error in the UI. Sorry!

TypeError: Cannot read properties of undefined (reading 'length') at x (http://localhost:5006/static/js/index.4_kdGSf3.js:269:43958) at L (http://localhost:5006/static/js/index.4_kdGSf3.js:89:206181) at WTe.render (http://localhost:5006/static/js/index.4_kdGSf3.js:89:190993) at Uk (http://localhost:5006/static/js/index.4_kdGSf3.js:49:6186) at VP (http://localhost:5006/static/js/index.4_kdGSf3.js:49:5982) at X8 (http://localhost:5006/static/js/index.4_kdGSf3.js:49:44939) at Y8 (http://localhost:5006/static/js/index.4_kdGSf3.js:49:39801) at vee (http://localhost:5006/static/js/index.4_kdGSf3.js:49:39728) at zx (http://localhost:5006/static/js/index.4_kdGSf3.js:49:39578) at Zk (http://localhost:5006/static/js/index.4_kdGSf3.js:49:35941)

How can we reproduce the issue?

  1. In a on budget account, create a split transaction (in my case, it was a two split), insert the category and value then save the transaction.
  2. Select the split transaction (the childs) and delete them (parent transaction is not deleted).
  3. Clicked on "Expand/Collapse split transaction" button on top right

Where are you hosting Actual?

Locally via Yarn

What browsers are you seeing the problem on?

Chrome

Operating System

Windows 11

Originally created by @zenmeow88 on GitHub (Feb 10, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? I'm currently running v25.2.1 on Chrome browser on Windows 11 desktop. Clicked on "Expand/Collapse split transaction" button on top right after deleted an existing split transactions, the error message below pop up. "Reset budget cache" and "Repair transaction" in the setting did not help, I had to use mobile (Android) to recreate the split or delete the "parent" transaction to resolve the issue. Unable to access to the following 3 pages after the error appeared: 1. All accounts 2. On budget 3. Specific account where the split transaction occured **Error Message:** Fatal Error There was an unrecoverable error in the UI. Sorry! TypeError: Cannot read properties of undefined (reading 'length') at x (http://localhost:5006/static/js/index.4_kdGSf3.js:269:43958) at L (http://localhost:5006/static/js/index.4_kdGSf3.js:89:206181) at WTe.render (http://localhost:5006/static/js/index.4_kdGSf3.js:89:190993) at Uk (http://localhost:5006/static/js/index.4_kdGSf3.js:49:6186) at VP (http://localhost:5006/static/js/index.4_kdGSf3.js:49:5982) at X8 (http://localhost:5006/static/js/index.4_kdGSf3.js:49:44939) at Y8 (http://localhost:5006/static/js/index.4_kdGSf3.js:49:39801) at vee (http://localhost:5006/static/js/index.4_kdGSf3.js:49:39728) at zx (http://localhost:5006/static/js/index.4_kdGSf3.js:49:39578) at Zk (http://localhost:5006/static/js/index.4_kdGSf3.js:49:35941) ### How can we reproduce the issue? 1. In a on budget account, create a split transaction (in my case, it was a two split), insert the category and value then save the transaction. 2. Select the split transaction (the childs) and delete them (parent transaction is not deleted). 3. Clicked on "Expand/Collapse split transaction" button on top right ### Where are you hosting Actual? Locally via Yarn ### What browsers are you seeing the problem on? Chrome ### Operating System Windows 11
GiteaMirror added the bug label 2026-02-28 19:56:16 -06:00
GiteaMirror commented 2026-02-28 19:56:16 -06:00
Author
Owner
Copy Link

@potatohead8 commented on GitHub (Feb 12, 2025):

+1 Came across the same fatal error. Similar stack trace, and similar repro steps:

TypeError: Cannot read properties of undefined (reading 'length') at x (http://192.168.2.6:8304/static/js/index.4_kdGSf3.js:269:43958) at L (http://192.168.2.6:8304/static/js/index.4_kdGSf3.js:89:206181) at WTe.render (http://192.168.2.6:8304/static/js/index.4_kdGSf3.js:89:190993) at Uk (http://192.168.2.6:8304/static/js/index.4_kdGSf3.js:49:6186) at VP (http://192.168.2.6:8304/static/js/index.4_kdGSf3.js:49:5982) at X8 (http://192.168.2.6:8304/static/js/index.4_kdGSf3.js:49:44939) at Y8 (http://192.168.2.6:8304/static/js/index.4_kdGSf3.js:49:39801) at vee (http://192.168.2.6:8304/static/js/index.4_kdGSf3.js:49:39728) at zx (http://192.168.2.6:8304/static/js/index.4_kdGSf3.js:49:39578) at Zk (http://192.168.2.6:8304/static/js/index.4_kdGSf3.js:49:35941)

@potatohead8 commented on GitHub (Feb 12, 2025): +1 Came across the same fatal error. Similar stack trace, and similar repro steps: ` TypeError: Cannot read properties of undefined (reading 'length') at x (http://192.168.2.6:8304/static/js/index.4_kdGSf3.js:269:43958) at L (http://192.168.2.6:8304/static/js/index.4_kdGSf3.js:89:206181) at WTe.render (http://192.168.2.6:8304/static/js/index.4_kdGSf3.js:89:190993) at Uk (http://192.168.2.6:8304/static/js/index.4_kdGSf3.js:49:6186) at VP (http://192.168.2.6:8304/static/js/index.4_kdGSf3.js:49:5982) at X8 (http://192.168.2.6:8304/static/js/index.4_kdGSf3.js:49:44939) at Y8 (http://192.168.2.6:8304/static/js/index.4_kdGSf3.js:49:39801) at vee (http://192.168.2.6:8304/static/js/index.4_kdGSf3.js:49:39728) at zx (http://192.168.2.6:8304/static/js/index.4_kdGSf3.js:49:39578) at Zk (http://192.168.2.6:8304/static/js/index.4_kdGSf3.js:49:35941) `
GiteaMirror commented 2026-02-28 19:56:17 -06:00
Author
Owner
Copy Link

@OskarZyg commented on GitHub (Feb 18, 2025):

May be related, I suspect the culprit is a messed up split transaction (I created a transfer, then split the resulting transaction into two categories, and after that I deleted them, causing a mess up somewhere along the way)

[Error] TypeError: undefined is not an object (evaluating 'Q.length')
x — TransactionsTable.jsx:1992
L — table.tsx:1056
render — FixedSizeList.tsx:234
Uk — react-dom.production.min.js:204:195
Y8 — react-dom.production.min.js:280:392
vee — react-dom.production.min.js:280:323
zx — react-dom.production.min.js:280:184
Zk — react-dom.production.min.js:271:91
V8 — react-dom.production.min.js:268:432
T — scheduler.production.min.js:13:205
N — scheduler.production.min.js:14:130

	Hk (index.4_kdGSf3.js:49:167)
	(anonymous function) (index.4_kdGSf3.js:49:680)
	$P (index.4_kdGSf3.js:47:9892)
	XP (index.4_kdGSf3.js:49:31905)
	W8 (index.4_kdGSf3.js:49:31485)
	gee (index.4_kdGSf3.js:49:31035)
	bee (index.4_kdGSf3.js:49:40940)
	Ou (index.4_kdGSf3.js:49:40295)
	V8 (index.4_kdGSf3.js:49:35197)
	T (index.4_kdGSf3.js:34:1554)
	N (index.4_kdGSf3.js:34:1913)

I'll try to debug this myself. In my case just the transaction loading in while scrolling causes causes the error.

@OskarZyg commented on GitHub (Feb 18, 2025): May be related, I suspect the culprit is a messed up split transaction (I created a transfer, then split the resulting transaction into two categories, and after that I deleted them, causing a mess up somewhere along the way) ``` [Error] TypeError: undefined is not an object (evaluating 'Q.length') x — TransactionsTable.jsx:1992 L — table.tsx:1056 render — FixedSizeList.tsx:234 Uk — react-dom.production.min.js:204:195 Y8 — react-dom.production.min.js:280:392 vee — react-dom.production.min.js:280:323 zx — react-dom.production.min.js:280:184 Zk — react-dom.production.min.js:271:91 V8 — react-dom.production.min.js:268:432 T — scheduler.production.min.js:13:205 N — scheduler.production.min.js:14:130 Hk (index.4_kdGSf3.js:49:167) (anonymous function) (index.4_kdGSf3.js:49:680) $P (index.4_kdGSf3.js:47:9892) XP (index.4_kdGSf3.js:49:31905) W8 (index.4_kdGSf3.js:49:31485) gee (index.4_kdGSf3.js:49:31035) bee (index.4_kdGSf3.js:49:40940) Ou (index.4_kdGSf3.js:49:40295) V8 (index.4_kdGSf3.js:49:35197) T (index.4_kdGSf3.js:34:1554) N (index.4_kdGSf3.js:34:1913) ``` I'll try to debug this myself. In my case just the transaction loading in while scrolling causes causes the error.
GiteaMirror commented 2026-02-28 19:56:17 -06:00
Author
Owner
Copy Link

@ngdbruce commented on GitHub (Feb 27, 2025):

May be related too.

TypeError: Cannot read properties of undefined (reading 'length') at x (https://budget.ngdluan.com/static/js/index.4_kdGSf3.js:269:43958) at L (https://budget.ngdluan.com/static/js/index.4_kdGSf3.js:89:206181) at WTe.render (https://budget.ngdluan.com/static/js/index.4_kdGSf3.js:89:190993) at Uk (https://budget.ngdluan.com/static/js/index.4_kdGSf3.js:49:6186) at VP (https://budget.ngdluan.com/static/js/index.4_kdGSf3.js:49:5982) at X8 (https://budget.ngdluan.com/static/js/index.4_kdGSf3.js:49:44939) at Y8 (https://budget.ngdluan.com/static/js/index.4_kdGSf3.js:49:39801) at vee (https://budget.ngdluan.com/static/js/index.4_kdGSf3.js:49:39728) at zx (https://budget.ngdluan.com/static/js/index.4_kdGSf3.js:49:39578) at Zk (https://budget.ngdluan.com/static/js/index.4_kdGSf3.js:49:35941)
@ngdbruce commented on GitHub (Feb 27, 2025): May be related too. ``` TypeError: Cannot read properties of undefined (reading 'length') at x (https://budget.ngdluan.com/static/js/index.4_kdGSf3.js:269:43958) at L (https://budget.ngdluan.com/static/js/index.4_kdGSf3.js:89:206181) at WTe.render (https://budget.ngdluan.com/static/js/index.4_kdGSf3.js:89:190993) at Uk (https://budget.ngdluan.com/static/js/index.4_kdGSf3.js:49:6186) at VP (https://budget.ngdluan.com/static/js/index.4_kdGSf3.js:49:5982) at X8 (https://budget.ngdluan.com/static/js/index.4_kdGSf3.js:49:44939) at Y8 (https://budget.ngdluan.com/static/js/index.4_kdGSf3.js:49:39801) at vee (https://budget.ngdluan.com/static/js/index.4_kdGSf3.js:49:39728) at zx (https://budget.ngdluan.com/static/js/index.4_kdGSf3.js:49:39578) at Zk (https://budget.ngdluan.com/static/js/index.4_kdGSf3.js:49:35941) ```
GiteaMirror commented 2026-02-28 19:56:18 -06:00
Author
Owner
Copy Link

@jfdoming commented on GitHub (Feb 27, 2025):

Hi folks! This should be fixed in #4465—if any of you have a moment, could you upload your budget to the preview and let me know if you still see problems? You can download your budget without crashing by manually going to /settings and clicking "Export data"; e.g., https://budget.ngdluan.com/settings or http://192.168.2.6:8304/settings.

Assuming the above fixes your issue, it will be in the next release. While you wait, you can upload your budget here instead and use the "Repair transactions" tool, and it should fix the budget. Steps:

  1. Download the budget as mentioned above (Settings > Export data).
  2. Upload the budget to the link.
  3. Go to Settings > "Repair transactions"
  4. Open the account that previously had problems—it should no longer have problems.
  5. Download the fixed budget and upload it back to your instance.

Sorry for the breakage here!

@jfdoming commented on GitHub (Feb 27, 2025): Hi folks! This should be fixed in #4465—if any of you have a moment, could you upload your budget to the [preview](https://deploy-preview-4465.demo.actualbudget.org/config-server) and let me know if you still see problems? You can download your budget without crashing by manually going to `/settings` and clicking "Export data"; e.g., https://budget.ngdluan.com/settings or http://192.168.2.6:8304/settings. Assuming the above fixes your issue, it will be in the next release. While you wait, you can upload your budget [here](https://deploy-preview-4464.demo.actualbudget.org/) instead and use the "Repair transactions" tool, and it _should_ fix the budget. Steps: 1. Download the budget as mentioned above (Settings > Export data). 2. Upload the budget to the [link](https://deploy-preview-4464.demo.actualbudget.org/). 3. Go to Settings > "Repair transactions" 4. Open the account that previously had problems—it should no longer have problems. 5. Download the fixed budget and upload it back to your instance. Sorry for the breakage here!
GiteaMirror commented 2026-02-28 19:56:18 -06:00
Author
Owner
Copy Link

@zenmeow88 commented on GitHub (Feb 27, 2025):

First of all, thanks for the fix!

I have tried the steps you outline above and below is the outcome:

  1. Deleting split transaction then clicking on the expand button is still producing the fatal error (as shown below). I'm not sure if this fix was intended to prevent future occurence or simply to repair existing error, so just letting you know.
  2. The "Repair transactions" tool is now working as intended, i.e. fixing the existing fatal error. Thanks.

TypeError: Cannot read properties of undefined (reading 'length') at T
(https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:269:43166) at B
(https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:89:208256) at LTe.render
(https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:89:193040) at Ak
(https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:6186) at FP
(https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:5982) at q8
(https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:44939) at W8
(https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:39801) at yee
(https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:39728) at $x
(https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:39578) at Vk
(https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:35941)

@zenmeow88 commented on GitHub (Feb 27, 2025): First of all, thanks for the fix! I have tried the steps you outline above and below is the outcome: 1. Deleting split transaction then clicking on the expand button is still producing the fatal error (as shown below). I'm not sure if this fix was intended to prevent future occurence or simply to repair existing error, so just letting you know. 2. The "Repair transactions" tool is now working as intended, i.e. fixing the existing fatal error. Thanks. TypeError: Cannot read properties of undefined (reading 'length') at T (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:269:43166) at B (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:89:208256) at LTe.render (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:89:193040) at Ak (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:6186) at FP (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:5982) at q8 (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:44939) at W8 (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:39801) at yee (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:39728) at $x (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:39578) at Vk (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:35941)
GiteaMirror commented 2026-02-28 19:56:18 -06:00
Author
Owner
Copy Link

@jfdoming commented on GitHub (Feb 27, 2025):

First of all, thanks for the fix!

I have tried the steps you outline above and below is the outcome:

  1. Deleting split transaction then clicking on the expand button is still producing the fatal error (as shown below). I'm not sure if this fix was intended to prevent future occurence or simply to repair existing error, so just letting you know.
  2. The "Repair transactions" tool is now working as intended, i.e. fixing the existing fatal error. Thanks.

TypeError: Cannot read properties of undefined (reading 'length') at T (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:269:43166) at B (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:89:208256) at LTe.render (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:89:193040) at Ak (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:6186) at FP (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:5982) at q8 (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:44939) at W8 (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:39801) at yee (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:39728) at $x (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:39578) at Vk (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:35941)

Interesting, can you share the exact steps you used to cause the error again? To be extra clear, there are two separate preview links. The first one should fix the error, and the second one has the "Repair transactions" option but won't fix the error. Were you seeing 1. occurring on both previews?

@jfdoming commented on GitHub (Feb 27, 2025): > First of all, thanks for the fix! > > I have tried the steps you outline above and below is the outcome: > > 1. Deleting split transaction then clicking on the expand button is still producing the fatal error (as shown below). I'm not sure if this fix was intended to prevent future occurence or simply to repair existing error, so just letting you know. > 2. The "Repair transactions" tool is now working as intended, i.e. fixing the existing fatal error. Thanks. > > TypeError: Cannot read properties of undefined (reading 'length') at T (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:269:43166) at B (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:89:208256) at LTe.render (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:89:193040) at Ak (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:6186) at FP (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:5982) at q8 (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:44939) at W8 (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:39801) at yee (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:39728) at $x (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:39578) at Vk (https://deploy-preview-4464.demo.actualbudget.org/static/js/index.uu9ZXVf5.js:49:35941) Interesting, can you share the exact steps you used to cause the error again? To be extra clear, there are two separate preview links. The first one _should_ fix the error, and the _second_ one has the "Repair transactions" option but won't fix the error. Were you seeing 1. occurring on both previews?
GiteaMirror commented 2026-02-28 19:56:18 -06:00
Author
Owner
Copy Link

@zenmeow88 commented on GitHub (Feb 27, 2025):

Interesting, can you share the exact steps you used to cause the error again? To be extra clear, there are two separate preview links. The first one should fix the error, and the second one has the "Repair transactions" option but won't fix the error. Were you seeing 1. occurring on both previews?

Ah, my bad I thought both are the same link, I only tested the second link in my first reply. But now I have also tested the first link, which has indeed fixed the fatal error (preventing the error)!

@zenmeow88 commented on GitHub (Feb 27, 2025): > Interesting, can you share the exact steps you used to cause the error again? To be extra clear, there are two separate preview links. The first one _should_ fix the error, and the _second_ one has the "Repair transactions" option but won't fix the error. Were you seeing 1. occurring on both previews? Ah, my bad I thought both are the same link, I only tested the second link in my first reply. But now I have also tested the first link, which has indeed fixed the fatal error (preventing the error)!
GiteaMirror commented 2026-02-28 19:56:19 -06:00
Author
Owner
Copy Link

@jfdoming commented on GitHub (Feb 27, 2025):

Interesting, can you share the exact steps you used to cause the error again? To be extra clear, there are two separate preview links. The first one should fix the error, and the second one has the "Repair transactions" option but won't fix the error. Were you seeing 1. occurring on both previews?

Ah, my bad I thought both are the same link, I only tested the second link in my first reply. But now I have also tested the first link, which has indeed fixed the fatal error (preventing the error)!

Amazing! We'll get this in for the next release, which will hopefully be out in a few days.

@jfdoming commented on GitHub (Feb 27, 2025): > > Interesting, can you share the exact steps you used to cause the error again? To be extra clear, there are two separate preview links. The first one _should_ fix the error, and the _second_ one has the "Repair transactions" option but won't fix the error. Were you seeing 1. occurring on both previews? > > Ah, my bad I thought both are the same link, I only tested the second link in my first reply. But now I have also tested the first link, which has indeed fixed the fatal error (preventing the error)! Amazing! We'll get this in for the next release, which will hopefully be out in a few days.
GiteaMirror commented 2026-02-28 19:56:19 -06:00
Author
Owner
Copy Link

@OskarZyg commented on GitHub (Feb 27, 2025):

I'm not sure how relevant to this issue what i'm about to say is, but I believe it's what caused my bug earlier so it may help:

Bank account sync through GoCardless, if you split a transaction from your bank into two categories, categorise them, then sync again, it duplicates and does something really weird which caused this error for me.

Apologies for the ambiguous language, I am going completely off memory.

@OskarZyg commented on GitHub (Feb 27, 2025): I'm not sure how relevant to _this_ issue what i'm about to say is, but I believe it's what caused my bug earlier so it may help: Bank account sync through GoCardless, if you split a transaction from your bank into two categories, categorise them, then sync again, it duplicates and does something really weird which caused this error for me. Apologies for the ambiguous language, I am going completely off memory.
GiteaMirror commented 2026-02-28 19:56:20 -06:00
Author
Owner
Copy Link

@jfdoming commented on GitHub (Feb 28, 2025):

I'm not sure how relevant to this issue what i'm about to say is, but I believe it's what caused my bug earlier so it may help:

Bank account sync through GoCardless, if you split a transaction from your bank into two categories, categorise them, then sync again, it duplicates and does something really weird which caused this error for me.

Apologies for the ambiguous language, I am going completely off memory.

@OskarZyg I would suggest creating a separate issue for this if you are able to come up with a repro. It sounds unrelated, though you still might try the steps mentioned above to see if they fix your issue.

@jfdoming commented on GitHub (Feb 28, 2025): > I'm not sure how relevant to _this_ issue what i'm about to say is, but I believe it's what caused my bug earlier so it may help: > > Bank account sync through GoCardless, if you split a transaction from your bank into two categories, categorise them, then sync again, it duplicates and does something really weird which caused this error for me. > > Apologies for the ambiguous language, I am going completely off memory. @OskarZyg I would suggest creating a separate issue for this if you are able to come up with a repro. It sounds unrelated, though you still might try the steps mentioned above to see if they fix your issue.
GiteaMirror commented 2026-02-28 19:56:20 -06:00
Author
Owner
Copy Link

@ngdbruce commented on GitHub (Feb 28, 2025):

Hi folks! This should be fixed in #4465—if any of you have a moment, could you upload your budget to the preview and let me know if you still see problems? You can download your budget without crashing by manually going to /settings and clicking "Export data"; e.g., https://budget.ngdluan.com/settings or http://192.168.2.6:8304/settings.

Assuming the above fixes your issue, it will be in the next release. While you wait, you can upload your budget here instead and use the "Repair transactions" tool, and it should fix the budget. Steps:

  1. Download the budget as mentioned above (Settings > Export data).
  2. Upload the budget to the link.
  3. Go to Settings > "Repair transactions"
  4. Open the account that previously had problems—it should no longer have problems.
  5. Download the fixed budget and upload it back to your instance.

Sorry for the breakage here!

Hi, actually I did not have a chance to follow your instruction. The thing is I did a workaround: I duplicated the budget file and everything work now. I deleted the old budget file already.
I am not so sure how I occured this issue but I already use "Repair transactions" and Cache fix but It didnt work. Hence, I can confirm duplicate the budget file and work on the new file will fix this issue.

@ngdbruce commented on GitHub (Feb 28, 2025): > Hi folks! This should be fixed in [#4465](https://github.com/actualbudget/actual/pull/4465)—if any of you have a moment, could you upload your budget to the [preview](https://deploy-preview-4465.demo.actualbudget.org/config-server) and let me know if you still see problems? You can download your budget without crashing by manually going to `/settings` and clicking "Export data"; e.g., https://budget.ngdluan.com/settings or http://192.168.2.6:8304/settings. > > Assuming the above fixes your issue, it will be in the next release. While you wait, you can upload your budget [here](https://deploy-preview-4464.demo.actualbudget.org/) instead and use the "Repair transactions" tool, and it _should_ fix the budget. Steps: > > 1. Download the budget as mentioned above (Settings > Export data). > 2. Upload the budget to the [link](https://deploy-preview-4464.demo.actualbudget.org/). > 3. Go to Settings > "Repair transactions" > 4. Open the account that previously had problems—it should no longer have problems. > 5. Download the fixed budget and upload it back to your instance. > > Sorry for the breakage here! Hi, actually I did not have a chance to follow your instruction. The thing is I did a workaround: I duplicated the budget file and everything work now. I deleted the old budget file already. I am not so sure how I occured this issue but I already use "Repair transactions" and Cache fix but It didnt work. Hence, I can confirm duplicate the budget file and work on the new file will fix this 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
tech-support
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#1849
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?