mirror of
https://github.com/actualbudget/actual.git
synced 2026-03-09 11:42:54 -05:00
[Bug]: February schedule not showing up as Upcoming #1916
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#1916
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 @joel-jeremy on GitHub (Mar 1, 2025).
Verified issue does not already exist?
What happened?
February schedule is skipped if schedule on 29th - 31th.
How can we reproduce the issue?
Steps to reproduce:
The February 2026 schedule is skipped and goes straight to March 30, 2026.
Where are you hosting Actual?
Fly.io
What browsers are you seeing the problem on?
Other
Operating System
Windows 11
@youngcw commented on GitHub (Mar 2, 2025):
Ive recommended people use the "last day" option to get around this.
@ftbboy2115 commented on GitHub (Mar 2, 2025):
Is this actually a bug? Or is this just how computers work, being very pedantic? 🤔😅
I think it would either require Actual needing to infer that when the user SAYS they want it to happen every nth day of the month, for it to assume otherwise, or else alert the user of what they've selected. For example, if they specify repeat every 31st, obviously that's only the last day of every other month. Maybe a notification letting the user know what they've specified, and the subsequent implications? Or maybe nothing needs to be done in Actual, but instead the docs can explain this behavior is to be expected.
@ftbboy2115 commented on GitHub (Mar 2, 2025):
I've updated the docs to explain the expected functionality, PR pending 👍🏼
https://actualbudget.org/docs/schedules
@Unostot commented on GitHub (Mar 2, 2025):
Well, "last day" is sometimes a viable workaround as soon as you know this option exists, and where to find it, but i guess some note in actual would be needed...
of course the docs can and should reflect it, but it will drive some people away, since the current way is the least expected one...and also easy to miss when starting, just to find out later that this feature is working in this way...
Especially since the "last day" option is also hard to find...
If you create a schedule from some transactions, it looks good: "each month, 30/31 set, click ok, go on to next schedule"...you just notice it later by chance that at least february is missing, or the monthly increases of some categories don't match the expected amount...(and this is something you don't want to think about, since you have started using actual for this calculation in the first place ;) )
I guess there is not one contract on earth, where you pay on the 30/31 of a month and in months that don't have this date, you must not pay ;)
So from my point of view:
Or even better: Move dates that don't exist in a month to the last available day in this month...
but maybe then the detection of transactions needs to be looked at. I'm not sure how the "inside two days" window is handled right now...
Greetings,
Uno
@joel-jeremy commented on GitHub (Mar 2, 2025):
This is what actually what happened to one of my installments that's supposed to happen every 29th. I was charged on March 1st. So I think it's good to match this behavior or maybe it can be auto converted to "last day".
One thing to note if we move it to March and post it, would it mark the March 29th schedule as Paid?
It's good that there is a workaround. But it feels kinda awkward especially if you have a schedule at the 29th (like myself) which is not actually the last day of the month.