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 #5433] [Bug]: Auto hold doesn't work for newly added income categories #9270

New Issue
Closed
opened 2026-04-10 19:32:41 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-10 19:32:41 -05:00
Owner
Copy Link

Originally created by @youngcw on GitHub (Jul 31, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/5433

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Found by discord user in https://discord.com/channels/937901803608096828/1400407650675458131

Auto hold isn't working on newly added income categories. Resetting the budget cache does fix the issue.

Steps to recreate:

  1. Open demo and add a new income category
  2. Enable auto hold on the new income category
  3. Add income transactions to the new income category
  4. See that nothing is being held when there should be

How can we reproduce the issue?

Steps to recreate:

  1. Open demo and add a new income category
  2. Enable auto hold on the new income category
  3. Add income transactions to the new income category
  4. See that nothing is being held when there should be

Where are you hosting Actual?

None

What browsers are you seeing the problem on?

No response

Operating System

None

Originally created by @youngcw on GitHub (Jul 31, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/5433 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? Found by discord user in https://discord.com/channels/937901803608096828/1400407650675458131 Auto hold isn't working on newly added income categories. Resetting the budget cache does fix the issue. Steps to recreate: 1. Open demo and add a new income category 2. Enable auto hold on the new income category 3. Add income transactions to the new income category 4. See that nothing is being held when there should be ### How can we reproduce the issue? Steps to recreate: 1. Open demo and add a new income category 2. Enable auto hold on the new income category 3. Add income transactions to the new income category 4. See that nothing is being held when there should be ### Where are you hosting Actual? None ### What browsers are you seeing the problem on? _No response_ ### Operating System None
GiteaMirror added the bug label 2026-04-10 19:32:41 -05:00
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
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#9270
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?