[Bug]: February schedule not showing up as Upcoming #1916

New Issue

GiteaMirror · 2026-02-28T19:58:23-06:00

GiteaMirror commented

2026-02-28 19:58:23 -06:00

Originally created by @joel-jeremy on GitHub (Mar 1, 2025).

Verified issue does not already exist?

I have searched and found no existing issue

What happened?

February schedule is skipped if schedule on 29th - 31th.

How can we reproduce the issue?

Steps to reproduce:

Go to schedules page
Create a recurring schedule on every 30th
Skip the next schedule until next February 2026

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

Originally created by @joel-jeremy on GitHub (Mar 1, 2025). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? February schedule is skipped if schedule on 29th - 31th. ### How can we reproduce the issue? Steps to reproduce: 1. Go to schedules page 2. Create a recurring schedule on every 30th 3. Skip the next schedule until next February 2026 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

GiteaMirror added the bug schedules labels 2026-02-28 19:58:23 -06:00

GiteaMirror closed this issue

2026-02-28 19:58:24 -06:00

GiteaMirror commented

2026-02-28 19:58:24 -06:00

@youngcw commented on GitHub (Mar 2, 2025):

Ive recommended people use the "last day" option to get around this.

@youngcw commented on GitHub (Mar 2, 2025): Ive recommended people use the "last day" option to get around this.

GiteaMirror commented

2026-02-28 19:58:24 -06:00

@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): 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.

GiteaMirror commented

2026-02-28 19:58:25 -06:00

@ftbboy2115 commented on GitHub (Mar 2, 2025):

I've updated the docs to explain the expected functionality, PR pending 👍🏼
https://actualbudget.org/docs/schedules

@ftbboy2115 commented on GitHub (Mar 2, 2025): I've updated the docs to explain the expected functionality, PR pending 👍🏼 https://actualbudget.org/docs/schedules

GiteaMirror commented

2026-02-28 19:58:25 -06:00

@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:

we need a very big bold note in the docs
some note in the schedule window

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

@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: * we need a very big bold note in the docs * some note in the schedule window 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

GiteaMirror commented

2026-02-28 19:58:26 -06:00

@joel-jeremy commented on GitHub (Mar 2, 2025):

Or even better: Move dates that don't exist in a month to the last available day in this month...

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?

Ive recommended people use the "last day" option to get around this.

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.

@joel-jeremy commented on GitHub (Mar 2, 2025): > Or even better: Move dates that don't exist in a month to the last available day in this month... 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? > Ive recommended people use the "last day" option to get around this. 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.