mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-16 07:04:23 -05:00
[GH-ISSUE #4215] [Bug]: Applying a budget template to month beyond a date driven saving target fails silently #8724
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#8724
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 @mullermn on GitHub (Jan 21, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4215
Verified issue does not already exist?
What happened?
Sorry for the word-soup title!
Budget templates are experimental so I don't fully trust them and I like to do a bit of sense checking to see if they are producing plausible looking numbers. Currently I have a category with this template:
#template 350 by 2025-02
#template 1000 by 2025-08
If I run the template for January or February, it runs and schedules an amount, but if I run it in March it fails silently - in fact the UI actively states that the template has been applied when it has not. I believe this is because the first template line will be out of date by March.
At a minimum the UX should be improved so that it's clear to the user that the template had no effect, though my proposal would be that Actual just ignore template lines for months in the past as sometimes it might be useful to preserve that history in the note rather than having to remove it.
This also removes the slight conceptual conflict of the templates existing in the 'timeless' category notes but their function taking effect in the time bound monthly columns. Currently when the real-world month advances the template system will stop working (refuse to run) until the user cleans up the templates and removes the now-out-of-date entries.
How can we reproduce the issue?
As above - just create a template with some scheduled budget template entries and attempt applying them before and after some of the deadlines.
Where are you hosting Actual?
Pikapods
What browsers are you seeing the problem on?
Desktop App (Electron)
Operating System
Mac OSX
@youngcw commented on GitHub (Jan 21, 2025):
This is what I get when running those templates in March. What client version are you using?
@mullermn commented on GitHub (Jan 22, 2025):
Client version: v25.1.0
Server version: v24.12.0
I believe that message comes up when the date in the template is in the past relative to the actual real world date - I saw it this month.
What I'm talking about is when the template date is in the future relative to real world but the past relative to the month in which you try and 'apply budget templates':
With the content as above:
#template 350 by 2025-02
#template 1000 by 2025-08
This gives me the
message, but no figure is put in to the budget. If I run 'check templates' from March's drop down it also reports that they all pass. I get the same behaviour for any month in advance of Feb 2025.
(To cover off the obvious - the amount available in the category in March is not sufficient to meet the August target, and there are funds available to budget)
@youngcw commented on GitHub (Jan 22, 2025):
Thats what I did. I applied those templates in March and got the error.
You should update your server. Its not ever recommended to run different server/client versions. There can be issues between the two if they are different. If you are using a desktop app and a server, I recommend using the PWA instead of the desktop app as the PWA will stay the same version as the server automatically.
@youngcw commented on GitHub (Jan 22, 2025):
Ok, so looks like the issue is that the error doesn't show if you apply to a single category, but it does show if you apply all the templates.
@youngcw commented on GitHub (Jan 23, 2025):
PR #4222 should fix you issue. Can you test that out?