github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 07:01:45 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[GH-ISSUE #2540] [Bug]: "Category is (nothing)" rule is not respected #7959

New Issue
Closed
opened 2026-04-10 18:05:50 -05:00 by GiteaMirror · 4 comments
GiteaMirror commented 2026-04-10 18:05:50 -05:00
Owner
Copy Link

Originally created by @SirJohnDoe on GitHub (Apr 2, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/2540

Verified issue does not already exist?

  • I have searched and found no existing issue

Is this related to GoCardless, Simplefin or another bank-sync provider?

  • I have checked my server logs and could not see any errors there
  • I will be attaching my server logs to this issue
  • I will be attaching my client-side (browser) logs to this issue
  • I understand that this issue will be automatically closed if insufficient information is provided

What happened?

Rules don't seem to be applied when I sync accounts through GoCardless. Below are the details of my latest transaction where it doesn't work, but it happens with all transactions I sync. First I thought it had to do with the stage of the rules, but for both 'Pre' en 'Default' it happens. The rule does detect the transaction though, see the screenshot below.

Rule:

image

The transaction in question in my browser log:

{
    "status": "ok",
    "data": {
        "iban": "WaPbJKjfoQRhEEhzxBQgnedbSUnIl53xYiTS9VU1dSc=",
        "balances": [
            {
                "balanceAmount": {
                    "amount": "53.29",
                    "currency": "EUR"
                },
                "balanceType": "closingBooked"
            }
        ],
        "institutionId": "OPENBANK_OPENESMM",
        "startingBalance": 0,
        "transactions": {
            "booked": [
                {
                    "bookingDate": "2024-04-02",
                    "valueDate": "2024-04-02",
                    "transactionAmount": {
                        "amount": "x",
                        "currency": "EUR"
                    },
                    "remittanceInformationUnstructured": "x",
                    "internalTransactionId": "eb9f10251615c90ec7945d75a934dbdc",
                    "date": "2024-04-02"
                },

Server log:

Available (first 10) transactions properties for new integration of institution in calculateStartingBalance function {
  balances: '[{"balanceAmount":{"amount":"53.29","currency":"EUR"},"balanceType":"closingBooked"}]',
  top10SortedTransactions: '[{"bookingDate":"2024-04-02","valueDate":"2024-04-02","transactionAmount":{"amount":"x","currency":"EUR"},"remittanceInformationUnstructured":"x","internalTransactionId":"eb9f10251615c90ec7945d75a934dbdc","date":"2024-04-02"},

Versions

Actual v24.4.0 running as addon on HassOS

What error did you receive?

No response

Where are you hosting Actual?

Other

What browsers are you seeing the problem on?

Chrome

Operating System

Windows 11

Originally created by @SirJohnDoe on GitHub (Apr 2, 2024). Original GitHub issue: https://github.com/actualbudget/actual/issues/2540 ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### Is this related to GoCardless, Simplefin or another bank-sync provider? - [X] I have checked my server logs and could not see any errors there - [X] I will be attaching my server logs to this issue - [X] I will be attaching my client-side (browser) logs to this issue - [X] I understand that this issue will be automatically closed if insufficient information is provided ### What happened? Rules don't seem to be applied when I sync accounts through GoCardless. Below are the details of my latest transaction where it doesn't work, but it happens with all transactions I sync. First I thought it had to do with the stage of the rules, but for both 'Pre' en 'Default' it happens. The rule does detect the transaction though, see the screenshot below. Rule: ![image](https://github.com/actualbudget/actual/assets/11654657/98dd3ada-b67f-49b6-8707-88d06b0d65aa) The transaction in question in my browser log: ``` { "status": "ok", "data": { "iban": "WaPbJKjfoQRhEEhzxBQgnedbSUnIl53xYiTS9VU1dSc=", "balances": [ { "balanceAmount": { "amount": "53.29", "currency": "EUR" }, "balanceType": "closingBooked" } ], "institutionId": "OPENBANK_OPENESMM", "startingBalance": 0, "transactions": { "booked": [ { "bookingDate": "2024-04-02", "valueDate": "2024-04-02", "transactionAmount": { "amount": "x", "currency": "EUR" }, "remittanceInformationUnstructured": "x", "internalTransactionId": "eb9f10251615c90ec7945d75a934dbdc", "date": "2024-04-02" }, ``` Server log: ``` Available (first 10) transactions properties for new integration of institution in calculateStartingBalance function { balances: '[{"balanceAmount":{"amount":"53.29","currency":"EUR"},"balanceType":"closingBooked"}]', top10SortedTransactions: '[{"bookingDate":"2024-04-02","valueDate":"2024-04-02","transactionAmount":{"amount":"x","currency":"EUR"},"remittanceInformationUnstructured":"x","internalTransactionId":"eb9f10251615c90ec7945d75a934dbdc","date":"2024-04-02"}, ``` **Versions** Actual v24.4.0 running as [addon](https://github.com/sztupy/hassio-actualbudget) on HassOS ### What error did you receive? _No response_ ### Where are you hosting Actual? Other ### What browsers are you seeing the problem on? Chrome ### Operating System Windows 11
GiteaMirror added the rulesbug labels 2026-04-10 18:05:50 -05:00
GiteaMirror commented 2026-04-10 18:05:52 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Apr 2, 2024):

👋 You might have another rule that clashes and gets applied before this one.

Try removing the "category is empty" condition and leaving only the imported payee.

<!-- gh-comment-id:2032623070 --> @MatissJanis commented on GitHub (Apr 2, 2024): 👋 You might have another rule that clashes and gets applied before this one. Try removing the "category is empty" condition and leaving only the imported payee.
GiteaMirror commented 2026-04-10 18:05:53 -05:00
Author
Owner
Copy Link

@SirJohnDoe commented on GitHub (Apr 3, 2024):

👋 You might have another rule that clashes and gets applied before this one.

Try removing the "category is empty" condition and leaving only the imported payee.

The rule for the transaction above is the second in the list, so I don't think that's the issue:

image

Why wouldn't Category is Empty work? I will try without it, but the reason I added it was because I only want it to apply to new transactions.

Edit: it seems to work without 'Category is nothing'

<!-- gh-comment-id:2034720394 --> @SirJohnDoe commented on GitHub (Apr 3, 2024): > 👋 You might have another rule that clashes and gets applied before this one. > > Try removing the "category is empty" condition and leaving only the imported payee. The rule for the transaction above is the second in the list, so I don't think that's the issue: ![image](https://github.com/actualbudget/actual/assets/11654657/15fb6d82-6934-4796-8bcd-36c313d40501) Why wouldn't Category is Empty work? I will try without it, but the reason I added it was because I only want it to apply to new transactions. Edit: it seems to work without 'Category is nothing'
GiteaMirror commented 2026-04-10 18:05:54 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Apr 3, 2024):

I can confirm: the issue is with "category is empty". We are currently not parsing these rules correctly.

The temporary workaround is to NOT use "is empty" expressions.

<!-- gh-comment-id:2035047495 --> @MatissJanis commented on GitHub (Apr 3, 2024): I can confirm: the issue is with "category is empty". We are currently not parsing these rules correctly. The temporary workaround is to NOT use "is empty" expressions.
GiteaMirror commented 2026-04-10 18:05:55 -05:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Jun 20, 2024):

Speculation as I've not looked into it, I wonder if it's a similar situation to #2790

Commenting so I can find this again, will have a look after work

<!-- gh-comment-id:2180665456 --> @matt-fidd commented on GitHub (Jun 20, 2024): Speculation as I've not looked into it, I wonder if it's a similar situation to #2790 Commenting so I can find this again, will have a look after work
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 rules
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#7959
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?