mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-11 09:32:33 -05:00
[Bug]: Rule to change CLEARED to false is getting run regardless of conditions #2539
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#2539
Reference in New Issue
Block a user
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?
Originally created by @natemeyerr-ctrl on GitHub (Oct 14, 2025).
Verified issue does not already exist?
What happened?
I created a rule to set the CLEARED flag to false on all imported transactions. The IF is amount < $10,000 (this is just a way to catch all rows), and the THEN is set cleared to false.
It works! The imported rows now import as uncleared.
However, everytime the rule runs, it marks all other previously imported transactions as uncleared. So now all my transactions on my chequing account are uncleared.
I also added another THEN to the rule just to see what rows it's actually meaning to update. I added THEN prepend to notes = TEST.
Imported, and the newly imported rows is uncleared, and it has TEST in the notes line.
However, all other rows in that account are now also uncleared, but there is no TEST in those rows.
So whenever you use cleared equals false in a rule it seems to clear all transactions in the account instead of just the imported transactions
How can we reproduce the issue?
Where are you hosting Actual?
Pikapods
What browsers are you seeing the problem on?
Chrome
Operating System
Windows 11
@youngcw commented on GitHub (Oct 14, 2025):
Are you using bank sync? My guess is that the problem is that the other transactions are getting imported and merged and thus rules are running on those transactions. Bank sync will import up to 90 days of transactions every sync, so your rule is being run on 90 days worth of transactions every time you sync.
I was not able to recreate this when using an ofx file as only a few of the transactions were getting "hit" by the import and only the new/modified transactions get the rule run.
@natemeyerr-ctrl commented on GitHub (Oct 14, 2025):
Yes. I'm using bank sync. What your saying makes sense.
The rule also adds the word test in front of the notes. Do you have an explanation on why the merged records don't receive the test but do receive the unclear flag?
@youngcw commented on GitHub (Oct 14, 2025):
Im only seeing the rule get applied to transactions that were part of the import. So no "test" and no unclearing of transactions that weren't imported or touched by the import.
@youngcw commented on GitHub (Oct 14, 2025):
If you want this rule to only apply to new transactions you will need to make your rule more complicated. For example, exclude transactions that have notes with "#Approved" in the un clear rule, then a separate rule that adds the "#Approved" tag to the notes at some point.
@natemeyerr-ctrl commented on GitHub (Oct 14, 2025):
Gotcha! I made the rule more complicated
I run Bank Sync
That new transaction (Youtube Premium) is imported and has #Imported in the NOTES. The cleared flag is also uncleared. However, the U-Haul transaction is also now UNCLEARED. even though it had #Imported in the notes.
I'm not sure what I'm missing here. But it seems there's a bug with the cleared flag, triggering on all transactions regardless of the criteria.
@youngcw commented on GitHub (Oct 14, 2025):
Ok, I am able to recreate it with these steps. I don't know whats happening, but the rule is getting applied to transactions it shouldn't. The rule edit page doesn't include the transactions marked as #IMPORTED but the rules are getting applied anyway.
I recreated it with both bank sync and OFX import so its probably an issue in the rules code directly.
@natemeyerr-ctrl commented on GitHub (Oct 15, 2025):
Thanks!