You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Actual also creates/updates rules for categorizing transactions. When you categorize a transaction, it will determine the best category for a transaction (basically the most common one) and create a rule that sets the category for the payee. If a rule already exists for the payee, it updates the category to set.
But after playing with it for a couple days, I find out that it did not automatically create rule when I categorized transactions.
Steps to reproduce:
import csv from bank
change category manually
check if there is any rule auto-created for this payee
Thanks
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Chrome, Safari
Operating System
Mac OSX
The text was updated successfully, but these errors were encountered:
Have you set the same payee to the same category multiple times? It wont make a rule unless you do the same thing a few times
kerhbal
changed the title
[Bug]: automatic rule for categorizing transactions is not working
[Bug]: Automatic rule for categorizing transactions is not working
Oct 31, 2024
@youngcw thanks for the lightning comment. No I probably didn't do multiple times for the same payee as I was also trying to create my own rules at the same time.
I tried again with some test samples and it worked! It created rule at around 3rd/4th categorizing
Will close the issue. Though it will be even better if there is a frontend msg to tell user a rule has just been created.
Verified issue does not already exist?
What happened?
So according to doc https://actualbudget.org/docs/budgeting/rules/#automatic-rules
But after playing with it for a couple days, I find out that it did not automatically create rule when I categorized transactions.
Steps to reproduce:
Thanks
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Chrome, Safari
Operating System
Mac OSX
The text was updated successfully, but these errors were encountered: