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]: Error during "clearing" a transaction with no Payee #726

New Issue
Closed
opened 2026-02-28 19:15:09 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-02-28 19:15:09 -06:00
Owner
Copy Link

Originally created by @KuroSetsuna29 on GitHub (Nov 11, 2023).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

When you try to clear a transaction that has no Payee set, I get the red "Something internally went wrong." toast message.

This also seems to break importing records, the record doesn't show up on the other accounts that have the Payee automatically set up as a transfer, unless I manually edit the record first. I think it fails processing an earlier transaction without a Payee and errors out without processing the rest of the records properly.

What error did you receive?

From the browser console:

[Exception] TypeError: Cannot destructure property 'transfer_acct' of '(intermediate value)' as it is null.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome

Operating System

Windows 10

Originally created by @KuroSetsuna29 on GitHub (Nov 11, 2023). ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? When you try to clear a transaction that has no Payee set, I get the red "Something internally went wrong." toast message. This also seems to break importing records, the record doesn't show up on the other accounts that have the Payee automatically set up as a transfer, unless I manually edit the record first. I think it fails processing an earlier transaction without a Payee and errors out without processing the rest of the records properly. ### What error did you receive? From the browser console: ``` [Exception] TypeError: Cannot destructure property 'transfer_acct' of '(intermediate value)' as it is null. ``` ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Chrome ### Operating System Windows 10
GiteaMirror added the bug label 2026-02-28 19:15:09 -06:00
GiteaMirror commented 2026-02-28 19:15:10 -06:00
Author
Owner
Copy Link

@shaankhosla commented on GitHub (Nov 12, 2023):

I'm not able to replicate this, could you provide a screenshot or a short screen recording with this bug on https://demo.actualbudget.org?

@shaankhosla commented on GitHub (Nov 12, 2023): I'm not able to replicate this, could you provide a screenshot or a short screen recording with this bug on https://demo.actualbudget.org?
GiteaMirror commented 2026-02-28 19:15:11 -06:00
Author
Owner
Copy Link

@KuroSetsuna29 commented on GitHub (Nov 12, 2023):

Hi, I was unable to replicate the issue on the demo site.

After debugging on my local instance I found the issue was that during import it was attempting to set the Payee to an non-existent Payee in the DB. It turned out I found some rules that was trying to set the Payee to a (deleted) payee. I am not sure how that payee was deleted, I could have possibly deleted that payee before and the Rule was just never updated.

It looks like after fixing the Rules that displayed (deleted) payee, all new imported transactions are fine, and after updating all the existing transactions by updating with a random Payee and then clearing it again seems to also fix the issue with the existing transactions.

Also, it looks like I was running version v23.10.0, and after upgrading to v23.11.0 I was unable to reproduce the error via the same steps. (I still see rule with (deleted) payee but no more errors while trying to import transactions with the matching rule)

Thanks for looking into this, sorry for the trouble. Since this seems to be fixed in new version I am closing this issue.

@KuroSetsuna29 commented on GitHub (Nov 12, 2023): Hi, I was unable to replicate the issue on the demo site. After debugging on my local instance I found the issue was that during import it was attempting to set the Payee to an non-existent Payee in the DB. It turned out I found some rules that was trying to set the Payee to a `(deleted)` payee. I am not sure how that payee was deleted, I could have possibly deleted that payee before and the Rule was just never updated. It looks like after fixing the Rules that displayed `(deleted)` payee, all new imported transactions are fine, and after updating all the existing transactions by updating with a random Payee and then clearing it again seems to also fix the issue with the existing transactions. Also, it looks like I was running version v23.10.0, and after upgrading to v23.11.0 I was unable to reproduce the error via the same steps. (I still see rule with `(deleted)` payee but no more errors while trying to import transactions with the matching rule) Thanks for looking into this, sorry for the trouble. Since this seems to be fixed in new version I am closing this issue.
GiteaMirror commented 2026-02-28 19:15:11 -06:00
Author
Owner
Copy Link

@shaankhosla commented on GitHub (Nov 12, 2023):

Awesome, glad it was fixed for you, no trouble at all!

@shaankhosla commented on GitHub (Nov 12, 2023): Awesome, glad it was fixed for you, no trouble at all!
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#726
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?