[Bug]: Budget templates do not fill categories for repeating schedules when currently completed #2887

Closed
opened 2026-02-28 20:31:41 -06:00 by GiteaMirror · 4 comments
Owner

Originally created by @Mansarde on GitHub (Feb 3, 2026).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Apply budget template will not fill categories marked as #template schedule SCHEDULE_NAME if the referenced (and repeating) schedule is currently marked as "Completed".

Only after restarting the repeating schedule (via Restart in the context-menu) will Apply budget template fill the budget category again.

This behavior makes sense for one-off schedules, but for repeating schedules the category in the month with the next due-date for that schedule should be filled when the template is applied there.

How can we reproduce the issue?

  1. Create a transaction that creates a positive "To Budget" value.

  2. Create a repeating (monthly) schedule called test.

  3. Add this note to a budget category: #template schedule test.

  4. Use Apply budget template on the previous month.
    => Notice that the budget category will be filled.

  5. Create a payment that will fulfill the schedule for that month, so that the schedule will be marked as "Completed".

  6. Go to the current month and try to apply the budget template there.
    => Notice how the budget category for the repeating schedule does NOT get filled!

  7. Restart the schedule, by right-clicking it (in the Schedule page) and clicking "Restart".

  8. Go back to the budget screen and apply the budget template again.
    => Notice how the budget category gets filled this time.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Other, Chrome

Operating System

Windows 11

Originally created by @Mansarde on GitHub (Feb 3, 2026). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? `Apply budget template` will not fill categories marked as `#template schedule SCHEDULE_NAME` if the referenced (and repeating) schedule is currently marked as "Completed". Only after restarting the repeating schedule (via `Restart` in the context-menu) will `Apply budget template` fill the budget category again. This behavior makes sense for one-off schedules, but for repeating schedules the category in the month with the next due-date for that schedule should be filled when the template is applied there. ### How can we reproduce the issue? 0. Create a transaction that creates a positive "To Budget" value. 1. Create a repeating (monthly) schedule called `test`. 2. Add this note to a budget category: `#template schedule test`. 3. Use `Apply budget template` on the previous month. => Notice that the budget category will be filled. 4. Create a payment that will fulfill the schedule for that month, so that the schedule will be marked as "Completed". 5. Go to the current month and try to apply the budget template there. => Notice how the budget category for the repeating schedule does NOT get filled! 6. Restart the schedule, by right-clicking it (in the Schedule page) and clicking "Restart". 7. Go back to the budget screen and apply the budget template again. => Notice how the budget category gets filled this time. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Other, Chrome ### Operating System Windows 11
GiteaMirror added the needs infobug labels 2026-02-28 20:31:41 -06:00
Author
Owner

@youngcw commented on GitHub (Feb 3, 2026):

If the schedule is still in use then why is it marked as completed?

@youngcw commented on GitHub (Feb 3, 2026): If the schedule is still in use then why is it marked as completed?
Author
Owner

@youngcw commented on GitHub (Feb 3, 2026):

In your description you seem to be mixing "completed" and "paid". Paid schedules will still fill, but completed schedules will be ignored. Im also not able to recreate the issue with your steps. Maybe you need more detail in the steps like the schedule start date, and the date of the posted transaction.

@youngcw commented on GitHub (Feb 3, 2026): In your description you seem to be mixing "completed" and "paid". Paid schedules will still fill, but completed schedules will be ignored. Im also not able to recreate the issue with your steps. Maybe you need more detail in the steps like the schedule start date, and the date of the posted transaction.
Author
Owner

@Mansarde commented on GitHub (Feb 3, 2026):

@youngcw Do "paid" entries of repeated payments not become "completed" some time after, while at the same time a new "upcoming" entry appears? 🤔

I thought this is how their states progress, but now I'm not so sure anymore.
Maybe I have mis-clicked something once for that particular entry, especially since it only happened to one entry.

Hmm, I'll close this issue then for now.
If I encounter it again and can reliably reproduce it, I'll make a new issue.

Sorry for the inconvenience!

@Mansarde commented on GitHub (Feb 3, 2026): @youngcw Do "paid" entries of repeated payments not become "completed" some time after, while at the same time a new "upcoming" entry appears? 🤔 I thought this is how their states progress, but now I'm not so sure anymore. Maybe I have mis-clicked something once for that particular entry, especially since it only happened to one entry. Hmm, I'll close this issue then for now. If I encounter it again and can reliably reproduce it, I'll make a new issue. Sorry for the inconvenience!
Author
Owner

@youngcw commented on GitHub (Feb 3, 2026):

I don't think any schedule will auto mark itself as complete. I may be wrong though

@youngcw commented on GitHub (Feb 3, 2026): I don't think any schedule will auto mark itself as complete. I may be wrong though
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#2887