github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-06 20:15:33 -05:00
Code Issues 1.5k Packages Projects Releases 55 Wiki Activity

[GH-ISSUE #7302] [Bug]: Post Rule Does Not Set Transaction as Cleared in Edge Build #17279

New Issue
Closed
opened 2026-04-14 20:10:38 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-14 20:10:38 -05:00
Owner
Copy Link

Originally created by @pasttree1790 on GitHub (Mar 27, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7302

What happened?

I use a Post rule to clear transactions from certain payees based on: https://actualbudget.org/docs/budgeting/rules/custom#q-i-have-accounts-like-cash-or-venmo-that-instantly-clear-at-the-moment-of-purchase-how-can-i-automate-toggling-the-cleared-status

The current Edge build and edge.actualbudget.org, do not clear the transaction when added via schedule or manually in the account register. I tried on demo.actualbudget.org, and the post rule successfully marks the transaction as cleared.

How can we reproduce the issue?

  1. Go to edge.actualbudget.org and open a demo file
  2. Create a new Post rule with the conditions matching a payee (i.e. "Dominion Power") and the action should set the transaction as cleared.
  3. Post the existing Schedule for "Dominion Power" (Utilities)
  4. Check the account register and see the transaction is not cleared.

Follow the same steps above on demo.actualbudget.org and see that the transaction is set to cleared.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Firefox

Operating System

Windows 11

Originally created by @pasttree1790 on GitHub (Mar 27, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7302 ### What happened? I use a Post rule to clear transactions from certain payees based on: https://actualbudget.org/docs/budgeting/rules/custom#q-i-have-accounts-like-cash-or-venmo-that-instantly-clear-at-the-moment-of-purchase-how-can-i-automate-toggling-the-cleared-status The current Edge build and edge.actualbudget.org, do not clear the transaction when added via schedule or manually in the account register. I tried on demo.actualbudget.org, and the post rule successfully marks the transaction as cleared. ### How can we reproduce the issue? 1. Go to edge.actualbudget.org and open a demo file 2. Create a new Post rule with the conditions matching a payee (i.e. "Dominion Power") and the action should set the transaction as cleared. 3. Post the existing Schedule for "Dominion Power" (Utilities) 4. Check the account register and see the transaction is not cleared. Follow the same steps above on demo.actualbudget.org and see that the transaction is set to cleared. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Firefox ### Operating System Windows 11
GiteaMirror added the regressionschedulesbug labels 2026-04-14 20:10:38 -05:00
GiteaMirror commented 2026-04-14 20:10:39 -05:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Mar 27, 2026):

Most likely https://github.com/actualbudget/actual/pull/7185

<!-- gh-comment-id:4145437861 --> @matt-fidd commented on GitHub (Mar 27, 2026): Most likely https://github.com/actualbudget/actual/pull/7185
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 regression schedules
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#17279
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?