mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-16 07:04:23 -05:00
[Bug]: Budget breaks for one month after resetting cache #2794
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#2794
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 @ja3cob on GitHub (Jan 8, 2026).
Verified issue does not already exist?
What happened?
EDIT: Exporting budget file and importing it again seems to resolve the issue. Having that in mind, I think it is still worth analysing this specific case to prevent it from happening again.
A very annoying bug happens in my budget. When I download the budget on a new device (or in privacy mode/after resetting all browser caches) a month's (september in particular) budget seems to be broken - my categories are overspent and there is money in "To Budget", despite I have earlier properly distributed this money. This waterfalls to breaking all budgets after september.
I found a way to "fix" that:
However this only fixes the issue for current cache. When I use a new device (or private mode) this appears again.
"Broken" september's budget:
Expected september's budget:
Fix demonstration:
How can we reproduce the issue?
I honestly have no clue how to reproduce this on a fresh budget file because it seems extremely case specific. I am however willing to provide my docker data for analysis, but despite anonymization I'd prefer to do it in a private message rather than publicly on GitHub as I use this personally for everyday expenses.
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Firefox, Chrome
Operating System
Windows 11
@youngcw commented on GitHub (Jan 9, 2026):
If we cant reproduce it then there is not really anything we can do to try and fix it.
@ja3cob commented on GitHub (Jan 9, 2026):
As I mentioned, I'd be happy to provide my data which you could use to debug the application and try to see whats the root cause of the issue
@youngcw commented on GitHub (Jan 9, 2026):
If importing a file fixes the issue, then I don't know what to do. I would need to import your export
@ja3cob commented on GitHub (Jan 9, 2026):
Importing the export does indeed fix the issue, therefore the only way could be directly using my actual-data dir (with server-files and user-files) (or in my case more specifically the docker volume)