[GH-ISSUE #7692] [Feedback]: Budget automation UI #117547

Open
opened 2026-06-11 12:47:01 -05:00 by GiteaMirror · 85 comments
Owner

Originally created by @matt-fidd on GitHub (May 3, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7692

Originally created by @matt-fidd on GitHub (May 3, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7692
GiteaMirror added the feedback label 2026-06-11 12:47:01 -05:00
Author
Owner

@shall0pass commented on GitHub (May 3, 2026):

UI Notification: Percent automations total 200% of income. Your percent automations add up to more than 100% and will be capped at 100%

I have two templates in this category:
#template 100% of previous Income-HSA
#template 100% of Interest-HSA

Both of these categories being referenced are separate Income categories. It just assigns last months income and this months interest to the budgeted cell. Because they are both unique income categories, I need to assign 100% of both. I feel the UI message is improper here and I am block from saving this in the UI.

<!-- gh-comment-id:4367351791 --> @shall0pass commented on GitHub (May 3, 2026): UI Notification: Percent automations total 200% of income. Your percent automations add up to more than 100% and will be capped at 100% I have two templates in this category: #template 100% of previous Income-HSA #template 100% of Interest-HSA Both of these categories being referenced are separate Income categories. It just assigns last months income and this months interest to the budgeted cell. Because they are both unique income categories, I need to assign 100% of both. I feel the UI message is improper here and I am block from saving this in the UI.
Author
Owner

@youngcw commented on GitHub (May 4, 2026):

Maybe cleanup templates should get ignored for now instead of causing an error.

<!-- gh-comment-id:4371634028 --> @youngcw commented on GitHub (May 4, 2026): Maybe cleanup templates should get ignored for now instead of causing an error.
Author
Owner

@matt-fidd commented on GitHub (May 4, 2026):

Maybe cleanup templates should get ignored for now instead of causing an error.

There is only one source of truth for the templates at the moment, you can't split them across UI and text based so I don't believe they'd even work if you migrated to UI and left them in the text. I'm aiming to do another "sprint" this month and get the rest of the template types supported as well as cleaning up anything people find during the month.

#goal directives need some real thinking about, I've still not worked out a good way to support them

<!-- gh-comment-id:4371677218 --> @matt-fidd commented on GitHub (May 4, 2026): > Maybe cleanup templates should get ignored for now instead of causing an error. There is only one source of truth for the templates at the moment, you can't split them across UI and text based so I don't believe they'd even work if you migrated to UI and left them in the text. I'm aiming to do another "sprint" this month and get the rest of the template types supported as well as cleaning up anything people find during the month. `#goal` directives need some real thinking about, I've still not worked out a good way to support them
Author
Owner

@youngcw commented on GitHub (May 4, 2026):

Do cleanup templates even look at the pref for where to run from? I guess if the notes are never parsed, then that would cause problems. I would have to look at the cleanup process

<!-- gh-comment-id:4371794965 --> @youngcw commented on GitHub (May 4, 2026): Do cleanup templates even look at the pref for where to run from? I guess if the notes are never parsed, then that would cause problems. I would have to look at the cleanup process
Author
Owner

@matt-fidd commented on GitHub (May 4, 2026):

I think my preferred philosophy for this feature is not to build any in-between processes, aside from the migration/unmigration layer. If we'd like support for a specific thing we should just add it to the UI instead of trying to work a way to run from both UI and text in the meantime.

That being said:

Do cleanup templates even look at the pref for where to run from? I guess if the notes are never parsed, then that would cause problems. I would have to look at the cleanup process

I've just had a look at the code and the cleanup templates are read directly from the notes when the button is pressed, and aren't actually persisted anywhere (!), which would not have been my guess as to how that worked. Given it works like that I don't mind allowing them to work in parallel.

Any ideas for how to implement the cleanup stuff in the UI would be welcome. From memory we need methods to support:

  • Global cleanup source
  • Global cleanup sink (allowing proportions to be set, default 1)
  • Category group scoped cleanup source
  • Category group scoped cleanup sink (allowing proportions to be set, default 1)
<!-- gh-comment-id:4372299589 --> @matt-fidd commented on GitHub (May 4, 2026): I think my preferred philosophy for this feature is not to build any in-between processes, aside from the migration/unmigration layer. If we'd like support for a specific thing we should just add it to the UI instead of trying to work a way to run from both UI and text in the meantime. That being said: > Do cleanup templates even look at the pref for where to run from? I guess if the notes are never parsed, then that would cause problems. I would have to look at the cleanup process I've just had a look at the code and the cleanup templates are read directly from the notes when the button is pressed, and aren't actually persisted anywhere (!), which would not have been my guess as to how that worked. Given it works like that I don't mind allowing them to work in parallel. Any ideas for how to implement the cleanup stuff in the UI would be welcome. From memory we need methods to support: - Global cleanup source - Global cleanup sink (allowing proportions to be set, default 1) - Category group scoped cleanup source - Category group scoped cleanup sink (allowing proportions to be set, default 1)
Author
Owner

@Juulz commented on GitHub (May 4, 2026):

Maybe cleanup templates should get ignored for now instead of causing an error.

There is only one source of truth for the templates at the moment, you can't split them across UI and text based so I don't believe they'd even work if you migrated to UI and left them in the text. I'm aiming to do another "sprint" this month and get the rest of the template types supported as well as cleaning up anything people find during the month.

#goal directives need some real thinking about, I've still not worked out a good way to support them

My thought is that they are an up to template that adds $0 and causes just a change in color variable based on the goal instead of the budget and a different tooltip. So, perhaps an up to template can have a checkbox to indicate if this is a goal? Only one up to per anyway, so this would work.

<!-- gh-comment-id:4372711664 --> @Juulz commented on GitHub (May 4, 2026): > > Maybe cleanup templates should get ignored for now instead of causing an error. > > There is only one source of truth for the templates at the moment, you can't split them across UI and text based so I don't believe they'd even work if you migrated to UI and left them in the text. I'm aiming to do another "sprint" this month and get the rest of the template types supported as well as cleaning up anything people find during the month. > > `#goal` directives need some real thinking about, I've still not worked out a good way to support them My thought is that they are an `up to` template that adds $0 and causes just a change in color variable based on the goal instead of the budget and a different tooltip. So, perhaps an `up to` template can have a checkbox to indicate if this is a goal? Only one `up to` per anyway, so this would work.
Author
Owner

@youngcw commented on GitHub (May 4, 2026):

If the limit value was moved into it own thing, and not in the list of automations, then there could also be a long term goal option with it. Both of those exists outside the regular templates. Something in the sidebar could work. So in addition to the add an automation button, there could be add limits and add long term goal buttons.

<!-- gh-comment-id:4373083790 --> @youngcw commented on GitHub (May 4, 2026): If the limit value was moved into it own thing, and not in the list of automations, then there could also be a long term goal option with it. Both of those exists outside the regular templates. Something in the sidebar could work. So in addition to the add an automation button, there could be add limits and add long term goal buttons.
Author
Owner

@Juulz commented on GitHub (May 9, 2026):

Here's an interesting case. I am paying off my mortgage early:

These are just simple budgets. 1800 monthly starting 05-01 and an additional 3200 monthly starting 06-01. There is 1800 in May's To Budget and >= 5000 in June. June's Budgeted is ZERO.

Image
Image
Image
Image
Image
Image
The **really** interesting thing is that they all budget the correct amount when the button is pressed!
<!-- gh-comment-id:4412546504 --> @Juulz commented on GitHub (May 9, 2026): Here's an interesting case. I am paying off my mortgage early: These are just simple budgets. 1800 monthly starting 05-01 and an additional 3200 monthly starting 06-01. There is 1800 in May's To Budget and >= 5000 in June. June's Budgeted is ZERO. <img width="1178" height="647" alt="Image" src="https://github.com/user-attachments/assets/ddf2dfcf-4c81-4658-a993-656bdff7be42" /> </br> <img width="1183" height="650" alt="Image" src="https://github.com/user-attachments/assets/912d8c85-686d-413b-bddf-cca513f7b282" /> </br> <img width="1188" height="644" alt="Image" src="https://github.com/user-attachments/assets/23a7211a-588b-491f-9da4-4d40231929af" /> </br> <img width="1186" height="619" alt="Image" src="https://github.com/user-attachments/assets/6cc9a85a-14a3-48af-859e-05c10711d4a9" /> </br> <img width="1191" height="619" alt="Image" src="https://github.com/user-attachments/assets/729e5632-e4bf-4706-8a79-b57f0eebb48c" /> </br> <img width="1183" height="641" alt="Image" src="https://github.com/user-attachments/assets/fb605a9a-6dd4-448e-ba49-f127a6c5cf89" /> </br> The **really** interesting thing is that they all budget the correct amount when the button is pressed!
Author
Owner

@totallynotjon commented on GitHub (May 10, 2026):

A UI to manage automation order across categories would be really useful. With a lot of priorities it gets cumbersome to figure out when something is running without opening each template individually. The new UI will actually make this harder to see at a glance than the notes version which you could hover.

If we make this change now, we could potentially simplify the UI to not even show the priority number and just have it a backend thing.

<!-- gh-comment-id:4416341108 --> @totallynotjon commented on GitHub (May 10, 2026): A UI to manage automation order across categories would be really useful. With a lot of priorities it gets cumbersome to figure out when something is running without opening each template individually. The new UI will actually make this harder to see at a glance than the notes version which you could hover. If we make this change now, we could potentially simplify the UI to not even show the priority number and just have it a backend thing.
Author
Owner

@matt-fidd commented on GitHub (May 11, 2026):

A UI to manage automation order across categories would be really useful. With a lot of priorities it gets cumbersome to figure out when something is running without opening each template individually. The new UI will actually make this harder to see at a glance than the notes version which you could hover.

If we make this change now, we could potentially simplify the UI to not even show the priority number and just have it a backend thing.

This is something we've been looking at adding as a stage here, something like the below?

Image
<!-- gh-comment-id:4419581273 --> @matt-fidd commented on GitHub (May 11, 2026): > A UI to manage automation order across categories would be really useful. With a lot of priorities it gets cumbersome to figure out when something is running without opening each template individually. The new UI will actually make this harder to see at a glance than the notes version which you could hover. > > If we make this change now, we could potentially simplify the UI to not even show the priority number and just have it a backend thing. This is something we've been looking at adding as a stage here, something like the below? <img width="1696" height="1054" alt="Image" src="https://github.com/user-attachments/assets/a04a2bb3-8a0b-45c7-949d-80acf5f061aa" />
Author
Owner

@matt-fidd commented on GitHub (May 11, 2026):

Here's an interesting case. I am paying off my mortgage early:

These are just simple budgets. 1800 monthly starting 05-01 and an additional 3200 monthly starting 06-01. There is 1800 in May's To Budget and >= 5000 in June. June's Budgeted is ZERO.
The really interesting thing is that they all budget the correct amount when the button is pressed!

I'd put money on this being a priority based issue. The first couple of screenshots show priority 0, with the others showing 150. The dry run engine runs all templates and returns the amount based on how much would be assigned based on priority (taking into account the money taken by higher priority templates). It makes sense if you were just applying single categories that the amount budgeted would be fixed.

Thinking about it in this context though, does taking priorities into account actually make sense? The system revolves around the amount of money in "To Budget", which we'd expect to be zero in future months, so looking at priorities would always skew it unless there was money available.

<!-- gh-comment-id:4419719566 --> @matt-fidd commented on GitHub (May 11, 2026): > Here's an interesting case. I am paying off my mortgage early: > > These are just simple budgets. 1800 monthly starting 05-01 and an additional 3200 monthly starting 06-01. There is 1800 in May's To Budget and >= 5000 in June. June's Budgeted is ZERO. > The **really** interesting thing is that they all budget the correct amount when the button is pressed! I'd put money on this being a priority based issue. The first couple of screenshots show priority `0`, with the others showing `150`. The dry run engine runs all templates and returns the amount based on how much would be assigned based on priority (taking into account the money taken by higher priority templates). It makes sense if you were just applying single categories that the amount budgeted would be fixed. Thinking about it in this context though, does taking priorities into account actually make sense? The system revolves around the amount of money in "To Budget", which we'd expect to be zero in future months, so looking at priorities would always skew it unless there was money available.
Author
Owner

@Juulz commented on GitHub (May 11, 2026):

Thinking about it in this context though, does taking priorities into account actually make sense? The system revolves around the amount of money in "To Budget", which we'd expect to be zero in future months, so looking at priorities would always skew it unless there was money available.

In the case of May - there was exactly 1800 in To Budget and all other templates had been run when I hit the category button. When I pressed the category button, 1800 was added. Even now, it still shows a projected number of $825.08 and To Budget is now ZERO. It just feels very random. I sure don't want to explain the math to new users! It adds an amount different from what it seems to say it's going to.

I think the average user will assume that it takes into account that they will be able to fund the category fully - that's the way I read the word "Projected". I project I can fund it fully! They may use that to pre-fund a checking account in the case where there are multiple templates (subs, etc.).

Maybe two amounts will make more sense to the end user? "Intended amount" and "Calculated amount"? Calculated amount should take To Budget into consideration. Personally, I want to see Intended amount so I know I built the budget correctly.

<!-- gh-comment-id:4420358571 --> @Juulz commented on GitHub (May 11, 2026): > Thinking about it in this context though, does taking priorities into account actually make sense? The system revolves around the amount of money in "To Budget", which we'd expect to be zero in future months, so looking at priorities would always skew it unless there was money available. In the case of May - there was exactly 1800 in To Budget and all other templates had been run when I hit the category button. When I pressed the category button, 1800 was added. Even now, it still shows a projected number of $825.08 and To Budget is now ZERO. It just feels very random. I sure don't want to explain the math to new users! It adds an amount different from what it seems to say it's going to. I think the average user will assume that it takes into account that they will be able to fund the category fully - that's the way I read the word "Projected". I project I can fund it fully! They may use that to pre-fund a checking account in the case where there are multiple templates (subs, etc.). Maybe two amounts will make more sense to the end user? "Intended amount" and "Calculated amount"? Calculated amount should take To Budget into consideration. Personally, I want to see Intended amount so I know I built the budget correctly.
Author
Owner

@Juulz commented on GitHub (May 11, 2026):

This is something we've been looking at adding as a stage here, something like the below?

Yes! Except, order within a group DOES matter!

<!-- gh-comment-id:4420380741 --> @Juulz commented on GitHub (May 11, 2026): > This is something we've been looking at adding as a stage here, something like the below? Yes! Except, order within a group DOES matter!
Author
Owner

@matt-fidd commented on GitHub (May 11, 2026):

Thinking about it in this context though, does taking priorities into account actually make sense? The system revolves around the amount of money in "To Budget", which we'd expect to be zero in future months, so looking at priorities would always skew it unless there was money available.

In the case of May - there was exactly 1800 in To Budget and all other templates had been run when I hit the category button. When I pressed the category button, 1800 was added. Even now, it still shows a projected number of $825.08 and To Budget is now ZERO. It just feels very random. I sure don't want to explain the math to new users! It adds an amount different from what it seems to say it's going to.

I think the average user will assume that it takes into account that they will be able to fund the category fully - that's the way I read the word "Projected". I project I can fund it fully! They may use that to pre-fund a checking account in the case where there are multiple templates (subs, etc.).

Maybe two amounts will make more sense to the end user? "Intended amount" and "Calculated amount"? Calculated amount should take To Budget into consideration. Personally, I want to see Intended amount so I know I built the budget correctly.

I imagine you get the "correct" numbers when you set the priority to 0. I agree with you though, try https://github.com/actualbudget/actual/pull/7790 when it builds and see if it's working for you.

<!-- gh-comment-id:4420452101 --> @matt-fidd commented on GitHub (May 11, 2026): > > Thinking about it in this context though, does taking priorities into account actually make sense? The system revolves around the amount of money in "To Budget", which we'd expect to be zero in future months, so looking at priorities would always skew it unless there was money available. > > In the case of May - there was exactly 1800 in To Budget and all other templates had been run when I hit the category button. When I pressed the category button, 1800 was added. Even now, it still shows a projected number of $825.08 and To Budget is now ZERO. It just feels very random. I sure don't want to explain the math to new users! It adds an amount different from what it seems to say it's going to. > > I think the average user will assume that it takes into account that they will be able to fund the category fully - that's the way I read the word "Projected". I project I can fund it fully! They may use that to pre-fund a checking account in the case where there are multiple templates (subs, etc.). > > Maybe two amounts will make more sense to the end user? "Intended amount" and "Calculated amount"? Calculated amount should take To Budget into consideration. Personally, I want to see Intended amount so I know I built the budget correctly. I imagine you get the "correct" numbers when you set the priority to 0. I agree with you though, try https://github.com/actualbudget/actual/pull/7790 when it builds and see if it's working for you.
Author
Owner

@Juulz commented on GitHub (May 11, 2026):

try #7790 when it builds and see if it's working for you.

Yes, it works great. The tooltip explains it well, also. 💯

<!-- gh-comment-id:4420649698 --> @Juulz commented on GitHub (May 11, 2026): > try [#7790](https://github.com/actualbudget/actual/pull/7790) when it builds and see if it's working for you. Yes, it works great. The tooltip explains it well, also. 💯
Author
Owner

@totallynotjon commented on GitHub (May 11, 2026):

A UI to manage automation order across categories would be really useful. With a lot of priorities it gets cumbersome to figure out when something is running without opening each template individually. The new UI will actually make this harder to see at a glance than the notes version which you could hover.

If we make this change now, we could potentially simplify the UI to not even show the priority number and just have it a backend thing.

This is something we've been looking at adding as a stage here, something like the below?

Image

This is really cool. I do like the idea of being able to group the automations and notate on them. Really glad this will hopefully be a part of the UI eventually.

Personal opinion but I do think getting rid of the priority messaging might make it easier to understand/use. Where before I would put something at the same priority to classify it to like needs or something, the group now covers that. And very few things would I actually want a random order to be taken between a few automations.

For instance each group could be orderable, and the priority is just managed underneath. Then the way things are seen are the order they are run.

There might be exceptions for this though, like the percentage of available funds might want to be on the same priority level.

<!-- gh-comment-id:4420941187 --> @totallynotjon commented on GitHub (May 11, 2026): > > A UI to manage automation order across categories would be really useful. With a lot of priorities it gets cumbersome to figure out when something is running without opening each template individually. The new UI will actually make this harder to see at a glance than the notes version which you could hover. > > > > If we make this change now, we could potentially simplify the UI to not even show the priority number and just have it a backend thing. > > This is something we've been looking at adding as a stage here, something like the below? > > <img width="1696" height="1054" alt="Image" src="https://github.com/user-attachments/assets/a04a2bb3-8a0b-45c7-949d-80acf5f061aa" /> This is really cool. I do like the idea of being able to group the automations and notate on them. Really glad this will hopefully be a part of the UI eventually. Personal opinion but I do think getting rid of the priority messaging might make it easier to understand/use. Where before I would put something at the same priority to classify it to like needs or something, the group now covers that. And very few things would I actually want a random order to be taken between a few automations. For instance each group could be orderable, and the priority is just managed underneath. Then the way things are seen are the order they are run. There might be exceptions for this though, like the percentage of available funds might want to be on the same priority level.
Author
Owner

@youngcw commented on GitHub (May 11, 2026):

One benefit of text templates is that its easy to add a description of what the template is for in the note. We should add some description or note field to each automation entry.

<!-- gh-comment-id:4422535421 --> @youngcw commented on GitHub (May 11, 2026): One benefit of text templates is that its easy to add a description of what the template is for in the note. We should add some description or note field to each automation entry.
Author
Owner

@iceita78 commented on GitHub (May 12, 2026):

Hey guys, wonderful job with the automation UI.
I'm playing with the features on https://edge.actualbudget.org/budget, but i noted something strange: when i put #goal 1000 for example on a category (on note field) this doesn't seems to work anymore when i press overwrite with templates.
Another question with automations "save by date", it seems that isn't possibile to set a single non recursive by date (i tried to put 0 on repeat every but it reset to 1), i'm missing something? Thank you again for the wonderful work

<!-- gh-comment-id:4429462382 --> @iceita78 commented on GitHub (May 12, 2026): Hey guys, wonderful job with the automation UI. I'm playing with the features on https://edge.actualbudget.org/budget, but i noted something strange: when i put #goal 1000 for example on a category (on note field) this doesn't seems to work anymore when i press overwrite with templates. Another question with automations "save by date", it seems that isn't possibile to set a single non recursive by date (i tried to put 0 on repeat every but it reset to 1), i'm missing something? Thank you again for the wonderful work
Author
Owner

@matt-fidd commented on GitHub (May 12, 2026):

Hey guys, wonderful job with the automation UI. I'm playing with the features on edge.actualbudget.org/budget, but i noted something strange: when i put #goal 1000 for example on a category (on note field) this doesn't seems to work anymore when i press overwrite with templates.

There is only one source of truth for automations, either the UI or notes. You can't run from both at the same time. I'll detail this in the docs before release, but if you'd like to use goal directives, you'll need to unmigrate that category back to notes until goals are added to the UI. They should be added soon by https://github.com/actualbudget/actual/pull/7792

Another question with automations "save by date", it seems that isn't possibile to set a single non recursive by date (i tried to put 0 on repeat every but it reset to 1), i'm missing something? Thank you again for the wonderful work

Good catch! Thank you. Addressed in https://github.com/actualbudget/actual/pull/7810

Image
<!-- gh-comment-id:4431091349 --> @matt-fidd commented on GitHub (May 12, 2026): > Hey guys, wonderful job with the automation UI. I'm playing with the features on [edge.actualbudget.org/budget](https://edge.actualbudget.org/budget), but i noted something strange: when i put #goal 1000 for example on a category (on note field) this doesn't seems to work anymore when i press overwrite with templates. There is only one source of truth for automations, either the UI or notes. You can't run from both at the same time. I'll detail this in the docs before release, but if you'd like to use `goal` directives, you'll need to unmigrate that category back to notes until goals are added to the UI. They should be added soon by https://github.com/actualbudget/actual/pull/7792 > Another question with automations "save by date", it seems that isn't possibile to set a single non recursive by date (i tried to put 0 on repeat every but it reset to 1), i'm missing something? Thank you again for the wonderful work Good catch! Thank you. Addressed in https://github.com/actualbudget/actual/pull/7810 <img width="962" height="758" alt="Image" src="https://github.com/user-attachments/assets/cba6f30e-2197-4cd1-9462-d5ea67c8c380" />
Author
Owner

@iceita78 commented on GitHub (May 12, 2026):

Hey guys, wonderful job with the automation UI. I'm playing with the features on edge.actualbudget.org/budget, but i noted something strange: when i put #goal 1000 for example on a category (on note field) this doesn't seems to work anymore when i press overwrite with templates.

There is only one source of truth for automations, either the UI or notes. You can't run from both at the same time. I'll detail this in the docs before release, but if you'd like to use goal directives, you'll need to unmigrate that category back to notes until goals are added to the UI. They should be added soon by #7792

Another question with automations "save by date", it seems that isn't possibile to set a single non recursive by date (i tried to put 0 on repeat every but it reset to 1), i'm missing something? Thank you again for the wonderful work

Good catch! Thank you. Addressed in #7810

Image

Hi Matt, ok thank you for the info and it's my pleasure in helping you with testing!

<!-- gh-comment-id:4434910660 --> @iceita78 commented on GitHub (May 12, 2026): > > Hey guys, wonderful job with the automation UI. I'm playing with the features on [edge.actualbudget.org/budget](https://edge.actualbudget.org/budget), but i noted something strange: when i put #goal 1000 for example on a category (on note field) this doesn't seems to work anymore when i press overwrite with templates. > > There is only one source of truth for automations, either the UI or notes. You can't run from both at the same time. I'll detail this in the docs before release, but if you'd like to use `goal` directives, you'll need to unmigrate that category back to notes until goals are added to the UI. They should be added soon by [#7792](https://github.com/actualbudget/actual/pull/7792) > > > Another question with automations "save by date", it seems that isn't possibile to set a single non recursive by date (i tried to put 0 on repeat every but it reset to 1), i'm missing something? Thank you again for the wonderful work > > Good catch! Thank you. Addressed in [#7810](https://github.com/actualbudget/actual/pull/7810) > > <img alt="Image" width="962" height="758" src="https://private-user-images.githubusercontent.com/81489167/591114499-cba6f30e-2197-4cd1-9462-d5ea67c8c380.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Nzg2MjA3NTcsIm5iZiI6MTc3ODYyMDQ1NywicGF0aCI6Ii84MTQ4OTE2Ny81OTExMTQ0OTktY2JhNmYzMGUtMjE5Ny00Y2QxLTk0NjItZDVlYTY3YzhjMzgwLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjA1MTIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwNTEyVDIxMTQxN1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTg0ZjQzNzM4ZGU0NDI4YTRlOWQ0MGQxMjE5NGM4YTBhYTYzMzNiOTllYmE4MDk5ZmE0YWU0NjY2NzUyYjgxNGEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JnJlc3BvbnNlLWNvbnRlbnQtdHlwZT1pbWFnZSUyRnBuZyJ9.zE4FNw92O8DEfmHvEVT8G80CZ9_8Y5FcHjnTYcJuN-M"> Hi Matt, ok thank you for the info and it's my pleasure in helping you with testing!
Author
Owner

@Juulz commented on GitHub (May 12, 2026):

Please change pageTextSubdued to pageTextLight. I think subdued should only be used for disabled text.

<!-- gh-comment-id:4434995642 --> @Juulz commented on GitHub (May 12, 2026): Please change pageTextSubdued to pageTextLight. I think subdued should only be used for disabled text.
Author
Owner

@matt-fidd commented on GitHub (May 12, 2026):

Please change pageTextSubdued to pageTextLight. I think subdued should only be used for disabled text.

Good call! https://github.com/actualbudget/actual/pull/7819 :)

<!-- gh-comment-id:4435040787 --> @matt-fidd commented on GitHub (May 12, 2026): > Please change pageTextSubdued to pageTextLight. I think subdued should only be used for disabled text. Good call! https://github.com/actualbudget/actual/pull/7819 :)
Author
Owner

@Juulz commented on GitHub (May 13, 2026):

Note: The descriptions in the sidebar are usually never complete and there's no way to see the rest of the words! I expected to see them all on hover, but nope. Either the boxes should expand to hold all the words instead of cutting them off or there should be a tooltip with all of the words.

Image Image




Also, The balance cap is now "below".

Image
<!-- gh-comment-id:4440244643 --> @Juulz commented on GitHub (May 13, 2026): Note: The descriptions in the sidebar are usually never complete and there's no way to see the rest of the words! I expected to see them all on hover, but nope. Either the boxes should expand to hold all the words instead of cutting them off or there should be a tooltip with all of the words. <img width="294" height="104" alt="Image" src="https://github.com/user-attachments/assets/d5a7ec54-0891-4330-9774-e8ad2cdc93fa" /> <img width="298" height="98" alt="Image" src="https://github.com/user-attachments/assets/1896aa43-d955-4d19-b7a5-4ab89b719a2d" /> </br></br> Also, The balance cap is now "below". <img width="305" height="101" alt="Image" src="https://github.com/user-attachments/assets/12d3d395-e800-4a45-bccb-ee23512ae697" />
Author
Owner

@Juulz commented on GitHub (May 13, 2026):

Are these types going to be included?

#template schedule {SCHEDULE NAME} [{increase/decrease} {number|number%}]
#template average {number} months [{increase/decrease} {number|number%}]

<!-- gh-comment-id:4440385131 --> @Juulz commented on GitHub (May 13, 2026): Are these types going to be included? `#template schedule {SCHEDULE NAME} [{increase/decrease} {number|number%}]` `#template average {number} months [{increase/decrease} {number|number%}]`
Author
Owner

@Juulz commented on GitHub (May 13, 2026):

It is a bit clunky to change the default amount. Clicking on the field should select the entire amount as it's the default behavior throughout the rest of the app.

<!-- gh-comment-id:4440878618 --> @Juulz commented on GitHub (May 13, 2026): It is a bit clunky to change the default amount. Clicking on the field should select the entire amount as it's the default behavior throughout the rest of the app.
Author
Owner

@Juulz commented on GitHub (May 13, 2026):

One benefit of text templates is that its easy to add a description of what the template is for in the note. We should add some description or note field to each automation entry.

If this is implemented, it would be cool to show the note(s) when you hover the clock icon.

<!-- gh-comment-id:4441088915 --> @Juulz commented on GitHub (May 13, 2026): > One benefit of text templates is that its easy to add a description of what the template is for in the note. We should add some description or note field to each automation entry. If this is implemented, it would be cool to show the note(s) when you hover the clock icon.
Author
Owner

@Juulz commented on GitHub (May 13, 2026):

Should Balance cap be allowed without an automation to accompany it? I don't think it does anything?

<!-- gh-comment-id:4441238884 --> @Juulz commented on GitHub (May 13, 2026): Should Balance cap be allowed without an automation to accompany it? I don't think it does anything?
Author
Owner

@totallynotjon commented on GitHub (May 13, 2026):

A problem with the parsing from the notes:
#template 0 up to 1000
This gets parsed as a refill to balance cap, when it is actually a balance cap and then fixed amount of 0 in the old system.

<!-- gh-comment-id:4442723925 --> @totallynotjon commented on GitHub (May 13, 2026): A problem with the parsing from the notes: #template 0 up to 1000 This gets parsed as a refill to balance cap, when it is actually a balance cap and then fixed amount of 0 in the old system.
Author
Owner

@matt-fidd commented on GitHub (May 13, 2026):

Description tooltip & balance cap description
Default amount preselected
Balance cap allowed on its own

@Juulz I've addressed your comments listed above in https://github.com/actualbudget/actual/pull/7832
I'll get the notes and increase/decrease ones in another. Thanks for your testing!

A problem with the parsing from the notes: #template 0 up to 1000 This gets parsed as a refill to balance cap, when it is actually a balance cap and then fixed amount of 0 in the old system.

@totallynotjon great catch, thank you for reporting, that should be fixed in the PR above too

<!-- gh-comment-id:4444825136 --> @matt-fidd commented on GitHub (May 13, 2026): > Description tooltip & balance cap description > Default amount preselected > Balance cap allowed on its own @Juulz I've addressed your comments listed above in https://github.com/actualbudget/actual/pull/7832 I'll get the notes and increase/decrease ones in another. Thanks for your testing! > A problem with the parsing from the notes: #template 0 up to 1000 This gets parsed as a refill to balance cap, when it is actually a balance cap and then fixed amount of 0 in the old system. @totallynotjon great catch, thank you for reporting, that should be fixed in the PR above too
Author
Owner

@youngcw commented on GitHub (May 13, 2026):

@totallynotjon Are you sure that is incorrect? The only use I can see of adding a #template 0 up to X line is to add a limit cap to a category with templates that don't include a limit already.

Splitting that into a limit cap and then a periodic template budgeting 0 still doesn't do anything, just the same as a single limit cap.

<!-- gh-comment-id:4445340552 --> @youngcw commented on GitHub (May 13, 2026): @totallynotjon Are you sure that is incorrect? The only use I can see of adding a `#template 0 up to X` line is to add a limit cap to a category with templates that don't include a limit already. Splitting that into a limit cap and then a periodic template budgeting 0 still doesn't do anything, just the same as a single limit cap.
Author
Owner

@matt-fidd commented on GitHub (May 13, 2026):

@totallynotjon Are you sure that is incorrect? The only use I can see of adding a #template 0 up to X line is to add a limit cap to a category with templates that don't include a limit already.

Agreed, but it's currently acting as if it was #template up to x by adding a refill automation

<!-- gh-comment-id:4445352770 --> @matt-fidd commented on GitHub (May 13, 2026): > [@totallynotjon](https://github.com/totallynotjon) Are you sure that is incorrect? The only use I can see of adding a `#template 0 up to X` line is to add a limit cap to a category with templates that don't include a limit already. Agreed, but it's currently acting as if it was `#template up to x` by adding a refill automation
Author
Owner

@youngcw commented on GitHub (May 13, 2026):

@totallynotjon Are you sure that is incorrect? The only use I can see of adding a #template 0 up to X line is to add a limit cap to a category with templates that don't include a limit already.

Agreed, but it's currently acting as if it was #template up to x by adding a refill automation

I guess as a single line it is more accurate to parse to two templates. The best thing probably would be to parse to two templates it it is the only line, then just a limit if there are others.

<!-- gh-comment-id:4445392695 --> @youngcw commented on GitHub (May 13, 2026): > > [@totallynotjon](https://github.com/totallynotjon) Are you sure that is incorrect? The only use I can see of adding a `#template 0 up to X` line is to add a limit cap to a category with templates that don't include a limit already. > > Agreed, but it's currently acting as if it was `#template up to x` by adding a refill automation I guess as a single line it is more accurate to parse to two templates. The best thing probably would be to parse to two templates it it is the only line, then just a limit if there are others.
Author
Owner

@matt-fidd commented on GitHub (May 13, 2026):

@totallynotjon Are you sure that is incorrect? The only use I can see of adding a #template 0 up to X line is to add a limit cap to a category with templates that don't include a limit already.

Agreed, but it's currently acting as if it was #template up to x by adding a refill automation

I guess as a single line it is more accurate to parse to two templates. The best thing probably would be to parse to two templates it it is the only line, then just a limit if there are others.

It's kind of a weird edge case, because you'd almost always be better off just tacking up to x on the end of another template. Capping if others exist makes sense, but I might leave it for another time. We'll see if anyone is really using these once this is out in 26.6

<!-- gh-comment-id:4445409247 --> @matt-fidd commented on GitHub (May 13, 2026): > > > [@totallynotjon](https://github.com/totallynotjon) Are you sure that is incorrect? The only use I can see of adding a `#template 0 up to X` line is to add a limit cap to a category with templates that don't include a limit already. > > > > > > Agreed, but it's currently acting as if it was `#template up to x` by adding a refill automation > > I guess as a single line it is more accurate to parse to two templates. The best thing probably would be to parse to two templates it it is the only line, then just a limit if there are others. It's kind of a weird edge case, because you'd almost always be better off just tacking `up to x` on the end of another template. Capping if others exist makes sense, but I might leave it for another time. We'll see if anyone is really using these once this is out in 26.6
Author
Owner

@totallynotjon commented on GitHub (May 13, 2026):

@totallynotjon Are you sure that is incorrect? The only use I can see of adding a #template 0 up to X line is to add a limit cap to a category with templates that don't include a limit already.

Agreed, but it's currently acting as if it was #template up to x by adding a refill automation

I guess as a single line it is more accurate to parse to two templates. The best thing probably would be to parse to two templates it it is the only line, then just a limit if there are others.

It's kind of a weird edge case, because you'd almost always be better off just tacking up to x on the end of another template. Capping if others exist makes sense, but I might leave it for another time. We'll see if anyone is really using these once this is out in 26.6

@youngcw @matt-fidd
Yah, it is a result of not all the template features having the "up to" syntax available. Percent type, schedule type etc. So the simplest way to set a limit was to just have a "0 up to y" as the first template line. I think this recommendation has been repeated in the discord so I wouldn't be surprised if at least a few others used it like this.

The only immediate need would be to at least respect it as "x up to y" and set a balance cap and a fixed. And the nicety is if x=0 then adding the fixed is unnecessary, because it really is just a standalone definition of a balance cap.

<!-- gh-comment-id:4445474608 --> @totallynotjon commented on GitHub (May 13, 2026): > > > > [@totallynotjon](https://github.com/totallynotjon) Are you sure that is incorrect? The only use I can see of adding a `#template 0 up to X` line is to add a limit cap to a category with templates that don't include a limit already. > > > > > > > > > Agreed, but it's currently acting as if it was `#template up to x` by adding a refill automation > > > > I guess as a single line it is more accurate to parse to two templates. The best thing probably would be to parse to two templates it it is the only line, then just a limit if there are others. > > It's kind of a weird edge case, because you'd almost always be better off just tacking `up to x` on the end of another template. Capping if others exist makes sense, but I might leave it for another time. We'll see if anyone is really using these once this is out in 26.6 @youngcw @matt-fidd Yah, it is a result of not all the template features having the "up to" syntax available. Percent type, schedule type etc. So the simplest way to set a limit was to just have a "0 up to y" as the first template line. I think this recommendation has been repeated in the discord so I wouldn't be surprised if at least a few others used it like this. The only immediate need would be to at least respect it as "x up to y" and set a balance cap and a fixed. And the nicety is if x=0 then adding the fixed is unnecessary, because it really is just a standalone definition of a balance cap.
Author
Owner

@matt-fidd commented on GitHub (May 17, 2026):

Are these types going to be included?

#template schedule {SCHEDULE NAME} [{increase/decrease} {number|number%}] #template average {number} months [{increase/decrease} {number|number%}]

Done! https://github.com/actualbudget/actual/pull/7881

<!-- gh-comment-id:4472553743 --> @matt-fidd commented on GitHub (May 17, 2026): > Are these types going to be included? > > `#template schedule {SCHEDULE NAME} [{increase/decrease} {number|number%}]` `#template average {number} months [{increase/decrease} {number|number%}]` Done! https://github.com/actualbudget/actual/pull/7881
Author
Owner

@youngcw commented on GitHub (May 19, 2026):

Being able to hover the notes icon and quickly see all the active templates is really nice. Adding in a similar functionality to the new icon would be a nice addition. The text could be cleanup up to be more clear than the raw template text where that was meant to be easy to parse, not just for reading.

<!-- gh-comment-id:4489927047 --> @youngcw commented on GitHub (May 19, 2026): Being able to hover the notes icon and quickly see all the active templates is really nice. Adding in a similar functionality to the new icon would be a nice addition. The text could be cleanup up to be more clear than the raw template text where that was meant to be easy to parse, not just for reading.
Author
Owner

@Juulz commented on GitHub (May 20, 2026):

Will we always allow notes #templates to function or will we turn them off at a point?

<!-- gh-comment-id:4498397863 --> @Juulz commented on GitHub (May 20, 2026): Will we always allow notes #templates to function or will we turn them off at a point?
Author
Owner

@matt-fidd commented on GitHub (May 20, 2026):

Will we always allow notes #templates to function or will we turn them off at a point?

I plan to phase them out when the UI is proven

<!-- gh-comment-id:4498510744 --> @matt-fidd commented on GitHub (May 20, 2026): > Will we always allow notes #templates to function or will we turn them off at a point? I plan to phase them out when the UI is proven
Author
Owner

@totallynotjon commented on GitHub (May 21, 2026):

Not the biggest issue but it would be nice to have a confirmation before deleting automation. Or have the hotkey functionality to undo and bring back the automation.

<!-- gh-comment-id:4509358931 --> @totallynotjon commented on GitHub (May 21, 2026): Not the biggest issue but it would be nice to have a confirmation before deleting automation. Or have the hotkey functionality to undo and bring back the automation.
Author
Owner

@totallynotjon commented on GitHub (May 21, 2026):

Not a huge issue but I think the up/down UI options are quite out of place. I can't remember these style of elements being used anywhere else so they are a bit jarring.

Image

Would expect something closer to the +/- options like in the rules editor.
Image

<!-- gh-comment-id:4509394382 --> @totallynotjon commented on GitHub (May 21, 2026): Not a huge issue but I think the up/down UI options are quite out of place. I can't remember these style of elements being used anywhere else so they are a bit jarring. <img width="390" height="146" alt="Image" src="https://github.com/user-attachments/assets/a70be27c-1d80-4d74-8f86-85d8ae459da2" /> Would expect something closer to the +/- options like in the rules editor. <img width="170" height="78" alt="Image" src="https://github.com/user-attachments/assets/9fdb354e-3a36-4b58-995c-30e884514b04" />
Author
Owner

@matt-fidd commented on GitHub (May 21, 2026):

Not a huge issue but I think the up/down UI options are quite out of place. I can't remember these style of elements being used anywhere else so they are a bit jarring.

Image Would expect something closer to the +/- options like in the rules editor. Image

Those are the browser default for number inputs, there are similar in use in the schedules modal. It would be nice to be able to style them but it's up to the browser how they're presented.

Image
<!-- gh-comment-id:4509433662 --> @matt-fidd commented on GitHub (May 21, 2026): > Not a huge issue but I think the up/down UI options are quite out of place. I can't remember these style of elements being used anywhere else so they are a bit jarring. > > <img alt="Image" width="390" height="146" src="https://private-user-images.githubusercontent.com/22186827/596166430-a70be27c-1d80-4d74-8f86-85d8ae459da2.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NzkzNzUyMTEsIm5iZiI6MTc3OTM3NDkxMSwicGF0aCI6Ii8yMjE4NjgyNy81OTYxNjY0MzAtYTcwYmUyN2MtMWQ4MC00ZDc0LThmODYtODVkOGFlNDU5ZGEyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjA1MjElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwNTIxVDE0NDgzMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWUxMjc1Yjc2YzNiMTNjMmYxOTdlYTBjYTU0NjExOTNiNDA0MTU1MGMxNDM3ODZlZmYwNDk0NTUzY2YyZGI2ZTMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JnJlc3BvbnNlLWNvbnRlbnQtdHlwZT1pbWFnZSUyRnBuZyJ9.8ahXSaQvrkt89y1MmJyAVZ33daKa1buEJfHvgR9cVhU"> > Would expect something closer to the +/- options like in the rules editor. <img alt="Image" width="170" height="78" src="https://private-user-images.githubusercontent.com/22186827/596165636-9fdb354e-3a36-4b58-995c-30e884514b04.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NzkzNzUyMTEsIm5iZiI6MTc3OTM3NDkxMSwicGF0aCI6Ii8yMjE4NjgyNy81OTYxNjU2MzYtOWZkYjM1NGUtM2EzNi00YjU4LTk5NWMtMzBlODg0NTE0YjA0LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjA1MjElMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwNTIxVDE0NDgzMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWE2NzFiYjE4MjJlYTRiMmZiYjliZDM4MzBhNWI5NjkwMjgzODUxY2M5ZTU3YjM3MjAyOGFjOWJkYjEwMWQ1OWMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JnJlc3BvbnNlLWNvbnRlbnQtdHlwZT1pbWFnZSUyRnBuZyJ9.klS_8HjeX9l0PUFv1be5dFyD7uPIXoPuqHucJld1eRI"> Those are the browser default for number inputs, there are similar in use in the schedules modal. It would be nice to be able to style them but it's up to the browser how they're presented. <img width="392" height="161" alt="Image" src="https://github.com/user-attachments/assets/4119081f-4458-4fd2-a39c-2ef820012536" />
Author
Owner

@mnil commented on GitHub (May 21, 2026):

@matt-fidd I thought it would be neat with sorting the schedules so created a PR:

<!-- gh-comment-id:4511422236 --> @mnil commented on GitHub (May 21, 2026): @matt-fidd I thought it would be neat with sorting the schedules so created a PR: - https://github.com/actualbudget/actual/pull/7913
Author
Owner

@matt-fidd commented on GitHub (May 21, 2026):

@matt-fidd I thought it would be neat with sorting the schedules so created a PR:

Amazing, thank you!

<!-- gh-comment-id:4511442535 --> @matt-fidd commented on GitHub (May 21, 2026): > [@matt-fidd](https://github.com/matt-fidd) I thought it would be neat with sorting the schedules so created a PR: > > * [[AI] Sort schedules alphabetically in Automations UI #7913](https://github.com/actualbudget/actual/pull/7913) Amazing, thank you!
Author
Owner

@youngcw commented on GitHub (May 29, 2026):

We should look at making the schedule templates use schedule IDs instead of names so if the name changes the template updates automatically.

<!-- gh-comment-id:4578602491 --> @youngcw commented on GitHub (May 29, 2026): We should look at making the schedule templates use schedule IDs instead of names so if the name changes the template updates automatically.
Author
Owner

@hypertxtc commented on GitHub (Jun 1, 2026):

The new budget templates UI is so cool! It does get a little funky on my laptop through.

Browser: Chrome
2560x1600 @ 200% display scaling. If I zoom out to 80% in Chrome it looks fine.

Image
<!-- gh-comment-id:4595200261 --> @hypertxtc commented on GitHub (Jun 1, 2026): The new budget templates UI is so cool! It does get a little funky on my laptop through. Browser: Chrome 2560x1600 @ 200% display scaling. If I zoom out to 80% in Chrome it looks fine. <img width="1938" height="1153" alt="Image" src="https://github.com/user-attachments/assets/2ed3f6db-93b2-4987-a28f-43ae24f64e6c" />
Author
Owner

@jpdsc commented on GitHub (Jun 1, 2026):

I have migrated most of my templates to the new Budget automation.
However, there 2 I cannot migrate because Budgdet automation does not support Completed schedules.

The scenario:
I set funds aside for the health insurance own risk cap. However, the own risk bucket is only used IF we make use of our health insurance.
When we do, I restart the schedule, update the date and amount, so I know when the payment is going to happen.
As you can see below, it is not finding the schedule because it's set as Completed.

Image

Perhaps an idea to also allow Completed schedules in Budget automation so when re-activated, they will work?

<!-- gh-comment-id:4595341218 --> @jpdsc commented on GitHub (Jun 1, 2026): I have migrated most of my templates to the new Budget automation. However, there 2 I cannot migrate because Budgdet automation does not support Completed schedules. The scenario: I set funds aside for the health insurance own risk cap. However, the own risk bucket is only used IF we make use of our health insurance. When we do, I restart the schedule, update the date and amount, so I know when the payment is going to happen. As you can see below, it is not finding the schedule because it's set as Completed. <img width="355" height="251" alt="Image" src="https://github.com/user-attachments/assets/74b2c73d-3d65-4d3d-b79f-0a5882243302" /> Perhaps an idea to also allow Completed schedules in Budget automation so when re-activated, they will work?
Author
Owner

@youngcw commented on GitHub (Jun 1, 2026):

I have migrated most of my templates to the new Budget automation. However, there 2 I cannot migrate because Budgdet automation does not support Completed schedules.

The scenario: I set funds aside for the health insurance own risk cap. However, the own risk bucket is only used IF we make use of our health insurance. When we do, I restart the schedule, update the date and amount, so I know when the payment is going to happen. As you can see below, it is not finding the schedule because it's set as Completed.

Image Perhaps an idea to also allow Completed schedules in Budget automation so when re-activated, they will work?

I feel like regular templates would be a lot more streamlined then that whole re-enable, save, complete process. Wouldn't something like a balance cap work better?

<!-- gh-comment-id:4595495974 --> @youngcw commented on GitHub (Jun 1, 2026): > I have migrated most of my templates to the new Budget automation. However, there 2 I cannot migrate because Budgdet automation does not support Completed schedules. > > The scenario: I set funds aside for the health insurance own risk cap. However, the own risk bucket is only used IF we make use of our health insurance. When we do, I restart the schedule, update the date and amount, so I know when the payment is going to happen. As you can see below, it is not finding the schedule because it's set as Completed. > > <img alt="Image" width="355" height="251" src="https://private-user-images.githubusercontent.com/7014736/601105028-74b2c73d-3d65-4d3d-b79f-0a5882243302.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODAzMzk0NDksIm5iZiI6MTc4MDMzOTE0OSwicGF0aCI6Ii83MDE0NzM2LzYwMTEwNTAyOC03NGIyYzczZC0zZDY1LTRkM2QtYjc5Zi0wYTU4ODIyNDMzMDIucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI2MDYwMSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNjA2MDFUMTgzOTA5WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NDE4MWM4YTVjODVkYjk3NGViMzllOGJlNWJlZjZhNzY3YWNjMTg2MTRlMWFlYWUwZDM3OTkzNDAyNjE0ODk5MiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmcmVzcG9uc2UtY29udGVudC10eXBlPWltYWdlJTJGcG5nIn0._zDxczFV69iw8i4caMqHgtqarCH5TyYV86_VB2KhmlY"> > Perhaps an idea to also allow Completed schedules in Budget automation so when re-activated, they will work? I feel like regular templates would be a lot more streamlined then that whole re-enable, save, complete process. Wouldn't something like a balance cap work better?
Author
Owner

@Juulz commented on GitHub (Jun 1, 2026):

When we do, I restart the schedule, update the date and amount, so I know when the payment is going to happen.

I have a few schedules I don't use all the time. I set them to $0.00 and just skip them when I don't need them.

<!-- gh-comment-id:4596750798 --> @Juulz commented on GitHub (Jun 1, 2026): > When we do, I restart the schedule, update the date and amount, so I know when the payment is going to happen. I have a few schedules I don't use all the time. I set them to $0.00 and just skip them when I don't need them.
Author
Owner

@youngcw commented on GitHub (Jun 1, 2026):

The automation descriptions in the hover popover doesn't specify if the end of month cleanup is a source/sink or both.

<!-- gh-comment-id:4596939083 --> @youngcw commented on GitHub (Jun 1, 2026): The automation descriptions in the hover popover doesn't specify if the end of month cleanup is a source/sink or both.
Author
Owner

@DerDomAusDo commented on GitHub (Jun 2, 2026):

I really like the new GUI, great work :) Would it be possible to show the full amount, that the schedule tries to reach, somewhere in the GUI,n ot only the monthly amount?
For example beside the monthly amount at the top-right corner:

Image

Or in the comment when hovering over the pie-chart-symbol?

<!-- gh-comment-id:4600040422 --> @DerDomAusDo commented on GitHub (Jun 2, 2026): I really like the new GUI, great work :) Would it be possible to show the full amount, that the schedule tries to reach, somewhere in the GUI,n ot only the monthly amount? For example beside the monthly amount at the top-right corner: <img width="200" height="59" alt="Image" src="https://github.com/user-attachments/assets/bccf9214-dd01-4ff6-a161-793849d00c85" /> Or in the comment when hovering over the pie-chart-symbol?
Author
Owner

@iceita78 commented on GitHub (Jun 2, 2026):

Hi guys, i have some problem with the desktop version, when i try to open the gui it seems to reload in loop (with flickering effect) and can't to do anything in it. I tried to ctrl R several times or reimport the budget but nothing seems to resolve the problem. While if i go on chrome with the edge version it works without problem. Any ideas?
Edit: I tried to do another test, imported in edge web version my budget, exported from there and tried to import in desktop version but it can't because see different version (i checked that the version are the same between edge web and desktop version)

<!-- gh-comment-id:4601162705 --> @iceita78 commented on GitHub (Jun 2, 2026): Hi guys, i have some problem with the desktop version, when i try to open the gui it seems to reload in loop (with flickering effect) and can't to do anything in it. I tried to ctrl R several times or reimport the budget but nothing seems to resolve the problem. While if i go on chrome with the edge version it works without problem. Any ideas? Edit: I tried to do another test, imported in edge web version my budget, exported from there and tried to import in desktop version but it can't because see different version (i checked that the version are the same between edge web and desktop version)
Author
Owner

@Juulz commented on GitHub (Jun 2, 2026):

Hi guys, i have some problem with the desktop version, when i try to open the gui it seems to reload in loop (with flickering effect) and can't to do anything in it. I tried to ctrl R several times or reimport the budget but nothing seems to resolve the problem. While if i go on chrome with the edge version it works without problem. Any ideas? Edit: I tried to do another test, imported in edge web version my budget, exported from there and tried to import in desktop version but it can't because see different version (i checked that the version are the same between edge web and desktop version)

I was able to reproduce this. Thread on discord: https://discord.com/channels/937901803608096828/1511363890343182396

<!-- gh-comment-id:4603180159 --> @Juulz commented on GitHub (Jun 2, 2026): > Hi guys, i have some problem with the desktop version, when i try to open the gui it seems to reload in loop (with flickering effect) and can't to do anything in it. I tried to ctrl R several times or reimport the budget but nothing seems to resolve the problem. While if i go on chrome with the edge version it works without problem. Any ideas? Edit: I tried to do another test, imported in edge web version my budget, exported from there and tried to import in desktop version but it can't because see different version (i checked that the version are the same between edge web and desktop version) I was able to reproduce this. Thread on discord: https://discord.com/channels/937901803608096828/1511363890343182396
Author
Owner

@matt-fidd commented on GitHub (Jun 2, 2026):

Hi guys, i have some problem with the desktop version, when i try to open the gui it seems to reload in loop (with flickering effect) and can't to do anything in it. I tried to ctrl R several times or reimport the budget but nothing seems to resolve the problem. While if i go on chrome with the edge version it works without problem. Any ideas? Edit: I tried to do another test, imported in edge web version my budget, exported from there and tried to import in desktop version but it can't because see different version (i checked that the version are the same between edge web and desktop version)

I was able to reproduce this. Thread on discord: discord.com/channels/937901803608096828/1511363890343182396

So windows desktop app related, interesting. Would appreciate some help in debugging this from anyone with a windows machine and the requisite skills. It looks like an infinite rerender issue, so something is unstable there.

<!-- gh-comment-id:4603234383 --> @matt-fidd commented on GitHub (Jun 2, 2026): > > Hi guys, i have some problem with the desktop version, when i try to open the gui it seems to reload in loop (with flickering effect) and can't to do anything in it. I tried to ctrl R several times or reimport the budget but nothing seems to resolve the problem. While if i go on chrome with the edge version it works without problem. Any ideas? Edit: I tried to do another test, imported in edge web version my budget, exported from there and tried to import in desktop version but it can't because see different version (i checked that the version are the same between edge web and desktop version) > > I was able to reproduce this. Thread on discord: [discord.com/channels/937901803608096828/1511363890343182396](https://discord.com/channels/937901803608096828/1511363890343182396) So windows desktop app related, interesting. Would appreciate some help in debugging this from anyone with a windows machine and the requisite skills. It looks like an infinite rerender issue, so something is unstable there.
Author
Owner

@iceita78 commented on GitHub (Jun 2, 2026):

Hi guys, i have some problem with the desktop version, when i try to open the gui it seems to reload in loop (with flickering effect) and can't to do anything in it. I tried to ctrl R several times or reimport the budget but nothing seems to resolve the problem. While if i go on chrome with the edge version it works without problem. Any ideas? Edit: I tried to do another test, imported in edge web version my budget, exported from there and tried to import in desktop version but it can't because see different version (i checked that the version are the same between edge web and desktop version)

I was able to reproduce this. Thread on discord: discord.com/channels/937901803608096828/1511363890343182396

So windows desktop app related, interesting. Would appreciate some help in debugging this from anyone with a windows machine and the requisite skills. It looks like an infinite rerender issue, so something is unstable there.

If it doesn't go too much deep in technical i can help you to debug this issue. Let me know what you need to test

<!-- gh-comment-id:4603304312 --> @iceita78 commented on GitHub (Jun 2, 2026): > > > Hi guys, i have some problem with the desktop version, when i try to open the gui it seems to reload in loop (with flickering effect) and can't to do anything in it. I tried to ctrl R several times or reimport the budget but nothing seems to resolve the problem. While if i go on chrome with the edge version it works without problem. Any ideas? Edit: I tried to do another test, imported in edge web version my budget, exported from there and tried to import in desktop version but it can't because see different version (i checked that the version are the same between edge web and desktop version) > > > > > > I was able to reproduce this. Thread on discord: [discord.com/channels/937901803608096828/1511363890343182396](https://discord.com/channels/937901803608096828/1511363890343182396) > > So windows desktop app related, interesting. Would appreciate some help in debugging this from anyone with a windows machine and the requisite skills. It looks like an infinite rerender issue, so something is unstable there. If it doesn't go too much deep in technical i can help you to debug this issue. Let me know what you need to test
Author
Owner

@Juulz commented on GitHub (Jun 2, 2026):

So windows desktop app related, interesting. Would appreciate some help in debugging this from anyone with a windows machine and the requisite skills. It looks like an infinite rerender issue, so something is unstable there.

Perhaps an Electron update is all that's needed? I can't find an update since v39, last of node.js 22. They are on v42 now, but use node.js 24. v39 is past EOL.

<!-- gh-comment-id:4603534455 --> @Juulz commented on GitHub (Jun 2, 2026): > So windows desktop app related, interesting. Would appreciate some help in debugging this from anyone with a windows machine and the requisite skills. It looks like an infinite rerender issue, so something is unstable there. Perhaps an Electron update is all that's needed? I can't find an update since v39, last of node.js 22. They are on v42 now, but use node.js 24. v39 is past EOL.
Author
Owner

@RedHare-Exe commented on GitHub (Jun 2, 2026):

Image

I find the "budget cap" UX a little confusing. I'd suggest the order and title of the boxes to be changed to be more similar to the "basic" automation for better understanding.

More like:

Image

The current design implies (at least to me) that the user is setting a cap on the budgeted amount, not the balance. Especially with the option for the cap to be negative.

Willing to reply for clarification!

<!-- gh-comment-id:4607698641 --> @RedHare-Exe commented on GitHub (Jun 2, 2026): <img width="960" height="495" alt="Image" src="https://github.com/user-attachments/assets/bfd37f80-9d0f-4a0c-9189-2e0a751d16e9" /> I find the "budget cap" UX a little confusing. I'd suggest the order and title of the boxes to be changed to be more similar to the "basic" automation for better understanding. More like: <img width="1284" height="276" alt="Image" src="https://github.com/user-attachments/assets/2c01d062-446f-465e-8872-e689f181eafe" /> The current design implies (at least to me) that the user is setting a cap on the budgeted amount, not the balance. Especially with the option for the cap to be negative. Willing to reply for clarification!
Author
Owner

@RedHare-Exe commented on GitHub (Jun 2, 2026):

Also, any thoughts on when this new UI could come to mobile? As you could previously edit templates from mobile by editing their notes.

<!-- gh-comment-id:4607782266 --> @RedHare-Exe commented on GitHub (Jun 2, 2026): Also, any thoughts on when this new UI could come to mobile? As you could previously edit templates from mobile by editing their notes.
Author
Owner

@YEGCSharpDev commented on GitHub (Jun 2, 2026):

One of the machines I use actual on is connected to TV, so huge screen. Text under Automation Type section is not aligning well.

Image
<!-- gh-comment-id:4607860245 --> @YEGCSharpDev commented on GitHub (Jun 2, 2026): One of the machines I use actual on is connected to TV, so huge screen. Text under Automation Type section is not aligning well. <img width="2462" height="1598" alt="Image" src="https://github.com/user-attachments/assets/d22ae2df-a197-4e76-8012-b762fdc0476f" />
Author
Owner

@YEGCSharpDev commented on GitHub (Jun 3, 2026):

One of the machines I use actual on is connected to TV, so huge screen. Text under Automation Type section is not aligning well.
Image

When I set the page to 80% or 90% zoom, the text is well aligned within the boxes. Checked in both Floorp (firefox fork) and Chromium. Same issue and same results.

<!-- gh-comment-id:4608597857 --> @YEGCSharpDev commented on GitHub (Jun 3, 2026): > One of the machines I use actual on is connected to TV, so huge screen. Text under Automation Type section is not aligning well. > <img alt="Image" width="2000" height="1298" src="https://private-user-images.githubusercontent.com/89283498/601877074-d22ae2df-a197-4e76-8012-b762fdc0476f.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODA0NTQwNjksIm5iZiI6MTc4MDQ1Mzc2OSwicGF0aCI6Ii84OTI4MzQ5OC82MDE4NzcwNzQtZDIyYWUyZGYtYTE5Ny00ZTc2LTgwMTItYjc2MmZkYzA0NzZmLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjA2MDMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwNjAzVDAyMjkyOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTk3ZjhiOTJjNmQwOTdmMDg5ZmRjYjM5YmUxYjZiNGRlNWQ0MDdmMzJjMjY4MDRjMzdhYjQ2MjJlZmNhMjkwNDkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JnJlc3BvbnNlLWNvbnRlbnQtdHlwZT1pbWFnZSUyRnBuZyJ9.BlMqaTP42DxJHkvBMZomP3aTKG_IaMRxwGqcHrCABas"> When I set the page to 80% or 90% zoom, the text is well aligned within the boxes. Checked in both Floorp (firefox fork) and Chromium. Same issue and same results.
Author
Owner

@matt-fidd commented on GitHub (Jun 3, 2026):

Thanks all for your reports of the modal not working on the Windows desktop app. This has now been fixed and updated builds are available at https://github.com/actualbudget/actual/actions/runs/26892032756

Be aware that this is technically a nightly release, and so once installed you may not be able to move backwards on to a stable version until v26.7.0 is published next month. Please make a backup of your budget file before install so that you can downgrade again if you wish.

<!-- gh-comment-id:4613951648 --> @matt-fidd commented on GitHub (Jun 3, 2026): Thanks all for your reports of the modal not working on the Windows desktop app. This has now been fixed and updated builds are available at https://github.com/actualbudget/actual/actions/runs/26892032756 Be aware that this is technically a `nightly` release, and so once installed you may not be able to move backwards on to a stable version until v26.7.0 is published next month. Please make a backup of your budget file before install so that you can downgrade again if you wish.
Author
Owner

@x-rous commented on GitHub (Jun 3, 2026):

Hi @matt-fidd, the budget automation UI looks great! one small feature idea I thought about for budget automation.

It would be useful to have an option to define different budget amounts by month within the same category.

For example:

Dec–Apr: 800
May: 900
Jun: 950
Jul: 1000
Aug: 1050
Sep: 1000
Oct: 950
Nov: 900

Or another example:

Aug: 2500
Feb: 3000
All other months: 1000

The current workaround is to create a monthly base amount, then add separate yearly top-up automations for the higher months with a yearly repeat. This works, but it becomes harder to maintain if the budget needs to increase next year, because multiple automations would need to be updated.

A “From History” automation can help, but it requires setting up the first year manually and is not as clear as defining the seasonal pattern directly.

Maybe there could be a new automation type like “Amount by Month”, “Monthly Schedule”, or “Seasonal Budget”, where the user can define the 12 monthly amounts in one place.

Optional fields could be:

  • Annual adjustment percentage: 0%, 3%, 5%, custom %
  • Adjustment frequency: every 12 months, 6 months, etc.

I am thinking about this mainly from a tracking budget view, so I am not sure if it would also make sense for envelope budgets.

<!-- gh-comment-id:4615600417 --> @x-rous commented on GitHub (Jun 3, 2026): Hi @matt-fidd, the budget automation UI looks great! one small feature idea I thought about for budget automation. It would be useful to have an option to define different budget amounts by month within the same category. For example: Dec–Apr: 800 May: 900 Jun: 950 Jul: 1000 Aug: 1050 Sep: 1000 Oct: 950 Nov: 900 Or another example: Aug: 2500 Feb: 3000 All other months: 1000 The current workaround is to create a monthly base amount, then add separate yearly top-up automations for the higher months with a yearly repeat. This works, but it becomes harder to maintain if the budget needs to increase next year, because multiple automations would need to be updated. A “From History” automation can help, but it requires setting up the first year manually and is not as clear as defining the seasonal pattern directly. Maybe there could be a new automation type like “Amount by Month”, “Monthly Schedule”, or “Seasonal Budget”, where the user can define the 12 monthly amounts in one place. Optional fields could be: - Annual adjustment percentage: 0%, 3%, 5%, custom % - Adjustment frequency: every 12 months, 6 months, etc. I am thinking about this mainly from a tracking budget view, so I am not sure if it would also make sense for envelope budgets.
Author
Owner

@james4141 commented on GitHub (Jun 4, 2026):

When using type 'From History', and you clear out (delete/backspace) the value in Number of months, it throws an error "safeNumber: number is not an integer: null". If you highlight the text and type a number, it works.

Image
<!-- gh-comment-id:4618164581 --> @james4141 commented on GitHub (Jun 4, 2026): When using type 'From History', and you clear out (delete/backspace) the value in Number of months, it throws an error "safeNumber: number is not an integer: null". If you highlight the text and type a number, it works. <img width="674" height="334" alt="Image" src="https://github.com/user-attachments/assets/853e56b5-553e-4853-accc-a1d3049dc426" />
Author
Owner

@laforcem commented on GitHub (Jun 4, 2026):

First off, thanks for this excellent new UI, it has been working quite well so far!

I have noticed that, while creating automations for a category, two automations of type "Cover schedule" will project a total of $0.00 when set to different priority values. The zero seems, from my investigation, intentional. However, the UI does not communicate this, so it's confusing for anyone trying to alter the priorities between the two automations.

Same priorities:

Image

Different priorities:

Image
<!-- gh-comment-id:4618874807 --> @laforcem commented on GitHub (Jun 4, 2026): First off, thanks for this excellent new UI, it has been working quite well so far! I have noticed that, while creating automations for a category, two automations of type "Cover schedule" will project a total of $0.00 when set to different priority values. The zero seems, from my investigation, intentional. However, the UI does not communicate this, so it's confusing for anyone trying to alter the priorities between the two automations. ### Same priorities: <img width="791" height="566" alt="Image" src="https://github.com/user-attachments/assets/3a46a3f0-664e-4d7c-afef-128085fdd422" /> ### Different priorities: <img width="787" height="568" alt="Image" src="https://github.com/user-attachments/assets/0c1276de-3b91-4c53-b98b-2fd0d6916005" />
Author
Owner

@Juulz commented on GitHub (Jun 4, 2026):

two automations of type "Cover schedule" will project a total of $0.00 when set to different priority values.

There is a warning about this in the docs for Cover schedule and Save by date automations.

<!-- gh-comment-id:4621504213 --> @Juulz commented on GitHub (Jun 4, 2026): > two automations of type "Cover schedule" will project a total of $0.00 when set to different priority values. There is a warning about this in the docs for _Cover schedule_ and _Save by date_ automations.
Author
Owner

@matt-fidd commented on GitHub (Jun 4, 2026):

To those of you who have had issues with the modal scaling on high dpi/zoomed devices, please could you try out this deploy preview and let me know if it's improved? I tried to recreate the situations with dev tools and it looked better to me.

https://deploy-preview-8080.demo.actualbudget.org/

<!-- gh-comment-id:4622228370 --> @matt-fidd commented on GitHub (Jun 4, 2026): To those of you who have had issues with the modal scaling on high dpi/zoomed devices, please could you try out this deploy preview and let me know if it's improved? I tried to recreate the situations with dev tools and it looked better to me. https://deploy-preview-8080.demo.actualbudget.org/
Author
Owner

@YEGCSharpDev commented on GitHub (Jun 4, 2026):

To those of you who have had issues with the modal scaling on high dpi/zoomed devices, please could you try out this deploy preview and let me know if it's improved? I tried to recreate the situations with dev tools and it looked better to me.

https://deploy-preview-8080.demo.actualbudget.org/

Yes! Its good now. I am able to zoom in and zoom out the text doesnt overflow.

Image
<!-- gh-comment-id:4622309991 --> @YEGCSharpDev commented on GitHub (Jun 4, 2026): > To those of you who have had issues with the modal scaling on high dpi/zoomed devices, please could you try out this deploy preview and let me know if it's improved? I tried to recreate the situations with dev tools and it looked better to me. > > https://deploy-preview-8080.demo.actualbudget.org/ Yes! Its good now. I am able to zoom in and zoom out the text doesnt overflow. <img width="2512" height="1649" alt="Image" src="https://github.com/user-attachments/assets/e5ec3db3-b804-4f84-95eb-84638c8a89f5" />
Author
Owner

@BipolarAnt commented on GitHub (Jun 4, 2026):

When using type 'From History', and you clear out (delete/backspace) the value in Number of months, it throws an error "safeNumber: number is not an integer: null". If you highlight the text and type a number, it works.

Came here to report the same issue. As long as the box is never blank, there's no issue, but the instant that it is empty, an error is thrown.

https://github.com/user-attachments/assets/8f598b8b-68df-4dbb-9949-fdc6aa32824e

<!-- gh-comment-id:4622617997 --> @BipolarAnt commented on GitHub (Jun 4, 2026): > When using type 'From History', and you clear out (delete/backspace) the value in Number of months, it throws an error "safeNumber: number is not an integer: null". If you highlight the text and type a number, it works. Came here to report the same issue. As long as the box is never blank, there's no issue, but the instant that it is empty, an error is thrown. https://github.com/user-attachments/assets/8f598b8b-68df-4dbb-9949-fdc6aa32824e
Author
Owner

@mnil commented on GitHub (Jun 4, 2026):

There is a bug when saving the full amount for a yearly schedule: https://github.com/actualbudget/actual/pull/8085

<!-- gh-comment-id:4625083824 --> @mnil commented on GitHub (Jun 4, 2026): There is a bug when saving the full amount for a yearly schedule: https://github.com/actualbudget/actual/pull/8085
Author
Owner

@matt-fidd commented on GitHub (Jun 5, 2026):

👀 Looking for testers for the mobile version of the UI in this PR, if anyone's interested!
https://deploy-preview-8099.demo.actualbudget.org/

<!-- gh-comment-id:4634330471 --> @matt-fidd commented on GitHub (Jun 5, 2026): 👀 Looking for testers for the mobile version of the UI in this PR, if anyone's interested! https://deploy-preview-8099.demo.actualbudget.org/
Author
Owner

@YEGCSharpDev commented on GitHub (Jun 6, 2026):

👀 Looking for testers for the mobile version of the UI in this PR, if anyone's interested! https://deploy-preview-8099.demo.actualbudget.org/

This works well. I tried doing create and edit workflows. Didn't run into any issues.

<!-- gh-comment-id:4636759900 --> @YEGCSharpDev commented on GitHub (Jun 6, 2026): > 👀 Looking for testers for the mobile version of the UI in this PR, if anyone's interested! https://deploy-preview-8099.demo.actualbudget.org/ This works well. I tried doing create and edit workflows. Didn't run into any issues.
Author
Owner

@x-rous commented on GitHub (Jun 6, 2026):

👀 Looking for testers for the mobile version of the UI in this PR, if anyone's interested!
https://deploy-preview-8099.demo.actualbudget.org/

Looking good, that's the only off bit I found.

image

<!-- gh-comment-id:4637978428 --> @x-rous commented on GitHub (Jun 6, 2026): > 👀 Looking for testers for the mobile version of the UI in this PR, if anyone's interested! > https://deploy-preview-8099.demo.actualbudget.org/ Looking good, that's the only off bit I found. ![image](https://github.com/user-attachments/assets/3b4d2f69-b57d-4392-92ef-061263bc0db7)
Author
Owner

@shawnsquire commented on GitHub (Jun 6, 2026):

Expectation: When setting the "From history" option, deleting the text in "Number of Months Back" should allow the user to type in a new number to an empty box.

Reality: After the text is cleared, the modal throws an error on the UI after the textbox briefly flashing nothing in the space.

Image Image
Something went wrong loading this section.
safeNumber: number is not an integer: null

Clicking "Try Again" resets the display without saving.

Workaround: Simply highlighting the text and replacing with a number without deleting will avoid the error.

<!-- gh-comment-id:4638090497 --> @shawnsquire commented on GitHub (Jun 6, 2026): **Expectation**: When setting the "From history" option, deleting the text in "Number of Months Back" should allow the user to type in a new number to an empty box. **Reality**: After the text is cleared, the modal throws an error on the UI after the textbox briefly flashing `nothing` in the space. <img width="834" height="772" alt="Image" src="https://github.com/user-attachments/assets/b8972801-fabf-44cf-a02b-b714635fc75a" /> <img width="478" height="152" alt="Image" src="https://github.com/user-attachments/assets/43278521-29d7-4d40-8b98-eb2406526b99" /> ``` Something went wrong loading this section. safeNumber: number is not an integer: null ``` Clicking "Try Again" resets the display without saving. **Workaround**: Simply highlighting the text and replacing with a number without deleting will avoid the error.
Author
Owner

@matt-fidd commented on GitHub (Jun 6, 2026):

Expectation: When setting the "From history" option, deleting the text in "Number of Months Back" should allow the user to type in a new number to an empty box.

Reality: After the text is cleared, the modal throws an error on the UI after the textbox briefly flashing nothing in the space.

Image Image
Something went wrong loading this section.
safeNumber: number is not an integer: null

Clicking "Try Again" resets the display without saving.

Workaround: Simply highlighting the text and replacing with a number without deleting will avoid the error.

Thanks for reporting! This was fixed in https://github.com/actualbudget/actual/pull/8082

<!-- gh-comment-id:4638330594 --> @matt-fidd commented on GitHub (Jun 6, 2026): > **Expectation**: When setting the "From history" option, deleting the text in "Number of Months Back" should allow the user to type in a new number to an empty box. > > **Reality**: After the text is cleared, the modal throws an error on the UI after the textbox briefly flashing `nothing` in the space. > > <img width="834" height="772" alt="Image" src="https://github.com/user-attachments/assets/b8972801-fabf-44cf-a02b-b714635fc75a" /> > > <img width="478" height="152" alt="Image" src="https://github.com/user-attachments/assets/43278521-29d7-4d40-8b98-eb2406526b99" /> > > ``` > Something went wrong loading this section. > safeNumber: number is not an integer: null > ``` > > Clicking "Try Again" resets the display without saving. > > **Workaround**: Simply highlighting the text and replacing with a number without deleting will avoid the error. > Thanks for reporting! This was fixed in https://github.com/actualbudget/actual/pull/8082
Author
Owner

@justalittle-BIT commented on GitHub (Jun 6, 2026):

On Firefox on Fedora 44, when editing the number of months to calculate the average, if i delete the prefilled value I get this error without hitting save

Image Image
<!-- gh-comment-id:4639760645 --> @justalittle-BIT commented on GitHub (Jun 6, 2026): On Firefox on Fedora 44, when editing the number of months to calculate the average, if i delete the prefilled value I get this error without hitting save <img width="1426" height="943" alt="Image" src="https://github.com/user-attachments/assets/6f46aa7f-417f-4bce-ac9a-93c3a0c06141" /> <img width="1426" height="943" alt="Image" src="https://github.com/user-attachments/assets/32d3168b-78a5-4508-9b9b-bf58668a0f47" />
Author
Owner

@matt-fidd commented on GitHub (Jun 6, 2026):

On Firefox on Fedora 44, when editing the number of months to calculate the average, if i delete the prefilled value I get this error without hitting save

Image Image

Thanks for reporting, as above this has been fixed in nightly now

<!-- gh-comment-id:4639772478 --> @matt-fidd commented on GitHub (Jun 6, 2026): > On Firefox on Fedora 44, when editing the number of months to calculate the average, if i delete the prefilled value I get this error without hitting save > > <img width="1426" height="943" alt="Image" src="https://github.com/user-attachments/assets/6f46aa7f-417f-4bce-ac9a-93c3a0c06141" /> > > <img width="1426" height="943" alt="Image" src="https://github.com/user-attachments/assets/32d3168b-78a5-4508-9b9b-bf58668a0f47" /> Thanks for reporting, as above this has been fixed in nightly now
Author
Owner

@PuddleOfFat commented on GitHub (Jun 7, 2026):

Would be nice to see the list of automations (when hovering over the icon on the budgets page) ordered by type, as opposed to sorting by time created. If I create multiple fixed amount automations, then set a balance cap and long term goal, then create more fixed amount automations, the order that's displayed on hover does not group them by type as I would expect.

On hover, it would be nice to see all automations grouped by type, so ALL fixed amount automations grouped and listed first, then balance cap, then long term goal, for example. As opposed to broken up, as shown in my screenshot.

Image Image
<!-- gh-comment-id:4641576734 --> @PuddleOfFat commented on GitHub (Jun 7, 2026): Would be nice to see the list of automations (when hovering over the icon on the budgets page) ordered by type, as opposed to sorting by time created. If I create multiple fixed amount automations, then set a balance cap and long term goal, then create more fixed amount automations, the order that's displayed on hover does not group them by type as I would expect. On hover, it would be nice to see all automations grouped by type, so ALL fixed amount automations grouped and listed first, then balance cap, then long term goal, for example. As opposed to broken up, as shown in my screenshot. <img width="471" height="391" alt="Image" src="https://github.com/user-attachments/assets/865bb585-a63e-4ba2-9ab6-6afd7576ab66" /> <img width="958" height="758" alt="Image" src="https://github.com/user-attachments/assets/841f3028-2d1f-4151-ac61-83462be4c5c6" />
Author
Owner

@remyayad commented on GitHub (Jun 7, 2026):

I'm facing a few issues with the Balance Cap feature in the UI. Created 2 separate issues to explain and document progress for others facing the same issues :

#8138 :

When configuring a Balance Cap on a weekly Fixed Amount automation, two bugs occur:

  1. The balance cap's starting date is generated as undefined by default, causing the budgeted amount to drop to zero.
  2. Even after the undefined date is resolved, the cap's starting date defaults to the current date rather than the automation's own starting date, making it impossible to apply the cap retroactively via the UI.

Bug 1 - starting undefined on Balance Cap

  1. Create a new Fixed Amount automation: $50 every week starting 2026-01-01
  2. Verify this works correctly - for January 2026 it projects $250 (2026-01-01 is a Thursday and there are 5 Thursdays in Jan 2026) :
Image
  1. Add a Balance Cap, set the period to weekly.
  2. Observe that the budgeted amount drops to $0.
Image
  1. Inspect the generated notes template - the balance cap line reads:
    #template-1 50 repeat every 1 weeks starting 2026-01-01
    #template O up to 85 per week starting undefined
Image

Workaround: Manually open the day-of-week dropdown in the Balance Cap and reselect the same day of the week (or any other day of the week). This triggers the date to be captured properly, changing starting undefined to starting 2026-06-07.

Image Image

Bug 2 - Balance Cap starting date defaults to corresponding day of day of the week in current week, not the automation's starting date

  1. After applying the workaround above (reselecting the day of the week), the generated template becomes:
    #template 50 repeat every 1 weeks starting 2026-01-01
    #template 0 up to 85 per week starting 2026-06-07

  2. Because the balance cap's starting date is 2026-06-07 (today) rather than 2026-01-01 (the automation's starting date), the cap does not apply to any months prior to June 2026.

  3. There is no way to set a custom starting date for the balance cap in the UI.

Expected: The balance cap's starting date should default to match the Fixed Amount automation's starting date (2026-01-01), or at minimum allow the user to set it manually.

Workaround:

  1. Note the generated template text.
  2. Unmigrate / switch to notes-based templates.
  3. Manually edit starting 2026-06-07starting 2026-01-01.
  4. Re-migrate back to UI automations.

Expected Final Template

#template 50 repeat every 1 weeks starting 2026-01-01
#template 0 up to 85 per week starting 2026-01-01


#8139 :

When a Fixed Amount automation with a Balance Cap is saved via the UI and then unmigrated to text-based templates, the balance cap is exposed as a separate #template 0 line. Re-migrating back to UI automations then creates a duplicate second automation with a value of zero, corrupting the configuration.

  1. Create a Fixed Amount automation with a Balance Cap via the UI and Save.
Image
  1. Re-open the automation form and click Unmigrate to switch to text-based templates.
  2. Observe that the notes now show two separate template lines - the fixed amount line and a separate #template 0 line representing the balance cap :
Image
  1. Re-open the UI automation form (re-migrate).
  2. Observe that a second automation is created with a value of $0, in addition to the original Fixed Amount automation.
Image

Expected Behavior

The UI should treat a Fixed Amount + Balance Cap as a single atomic automation. Unmigrating and re-migrating should produce the same single automation, not two.


Actual Behavior

  • Unmigrating exposes the balance cap as a standalone #template 0 line.
  • Re-migrating interprets that line as an independent automation, resulting in a duplicate $0 automation being added alongside the original.
<!-- gh-comment-id:4643466235 --> @remyayad commented on GitHub (Jun 7, 2026): I'm facing a few issues with the Balance Cap feature in the UI. Created 2 separate issues to explain and document progress for others facing the same issues : #8138 : When configuring a **Balance Cap** on a weekly Fixed Amount automation, two bugs occur: 1. The balance cap's `starting` date is generated as `undefined` by default, causing the budgeted amount to drop to zero. 2. Even after the `undefined` date is resolved, the cap's starting date defaults to the current date rather than the automation's own starting date, making it impossible to apply the cap retroactively via the UI. ### Bug 1 - `starting undefined` on Balance Cap 1. Create a new Fixed Amount automation: `$50 every week starting 2026-01-01` 2. Verify this works correctly - for January 2026 it projects **$250** (2026-01-01 is a Thursday and there are 5 Thursdays in Jan 2026) : <img width="953" height="755" alt="Image" src="https://github.com/user-attachments/assets/b09505b2-3c6b-4906-96cd-61ca9f8f5f2c" /> 3. Add a Balance Cap, set the period to **weekly**. 4. Observe that the budgeted amount **drops to $0**. <img width="957" height="758" alt="Image" src="https://github.com/user-attachments/assets/96a1b0a1-9a3d-47e8-ab36-438c8087094e" /> 5. Inspect the generated notes template - the balance cap line reads: `#template-1 50 repeat every 1 weeks starting 2026-01-01` `#template O up to 85 per week starting undefined` <img width="922" height="735" alt="Image" src="https://github.com/user-attachments/assets/8bffec08-17a9-45c9-8a1e-0809cd3d4e8c" /> **Workaround:** Manually open the day-of-week dropdown in the Balance Cap and reselect the same day of the week (or any other day of the week). This triggers the date to be captured properly, changing `starting undefined` to `starting 2026-06-07`. <img width="954" height="756" alt="Image" src="https://github.com/user-attachments/assets/33316196-915d-40fa-a05a-f373a2e9e128" /> <img width="913" height="729" alt="Image" src="https://github.com/user-attachments/assets/2115e1f4-5372-42a0-95fc-4ce2b37f8ebd" /> --- ### Bug 2 - Balance Cap starting date defaults to corresponding day of day of the week in current week, not the automation's starting date 1. After applying the workaround above (reselecting the day of the week), the generated template becomes: `#template 50 repeat every 1 weeks starting 2026-01-01` `#template 0 up to 85 per week starting 2026-06-07` 2. Because the balance cap's starting date is `2026-06-07` (today) rather than `2026-01-01` (the automation's starting date), the cap does not apply to any months prior to June 2026. 3. There is no way to set a custom starting date for the balance cap in the UI. **Expected:** The balance cap's starting date should default to match the Fixed Amount automation's starting date (`2026-01-01`), or at minimum allow the user to set it manually. **Workaround:** 1. Note the generated template text. 2. Unmigrate / switch to notes-based templates. 3. Manually edit `starting 2026-06-07` → `starting 2026-01-01`. 4. Re-migrate back to UI automations. --- ## Expected Final Template `#template 50 repeat every 1 weeks starting 2026-01-01` `#template 0 up to 85 per week starting 2026-01-01` --- #8139 : When a **Fixed Amount** automation with a **Balance Cap** is saved via the UI and then unmigrated to text-based templates, the balance cap is exposed as a separate `#template 0` line. Re-migrating back to UI automations then creates a **duplicate second automation** with a value of zero, corrupting the configuration. 1. Create a Fixed Amount automation with a Balance Cap via the UI and **Save**. <img width="957" height="755" alt="Image" src="https://github.com/user-attachments/assets/07e8a380-35c3-4893-b202-80c915e0b063" /> 2. Re-open the automation form and click **Unmigrate** to switch to text-based templates. 3. Observe that the notes now show **two separate template lines** - the fixed amount line and a separate `#template 0` line representing the balance cap : <img width="911" height="705" alt="Image" src="https://github.com/user-attachments/assets/c0495f9b-6ba8-4365-8169-e2d3c60d062b" /> 4. Re-open the UI automation form (re-migrate). 5. Observe that a **second automation is created** with a value of `$0`, in addition to the original Fixed Amount automation. <img width="957" height="756" alt="Image" src="https://github.com/user-attachments/assets/8e1850dc-41f1-4885-a4c2-c8a1c0d06c87" /> --- ## Expected Behavior The UI should treat a Fixed Amount + Balance Cap as a **single atomic automation**. Unmigrating and re-migrating should produce the same single automation, not two. --- ## Actual Behavior - Unmigrating exposes the balance cap as a standalone `#template 0` line. - Re-migrating interprets that line as an independent automation, resulting in a duplicate `$0` automation being added alongside the original.
Author
Owner

@Kennedy242 commented on GitHub (Jun 7, 2026):

Image Image

Why must I remove past targets in order for the Budget Automation to run?

I have automation so save $900 for my car for June 2026. When I run the automation for July 2026 I get an error that the target month has passed and I must remove that automation to run the Budget Automation. Why? I feel like if the target month has passed, no more money would be set aside for that target. I think the design should be changed so that if target has passed that automation will just do nothing, not error. ( maybe provide a warning or info? )

When Check Template is run, they report as all passed, it seems that either the same error should show up in Check Template or that Budget Automation should run?

Also in this example. I have $1300 in Car Expense Category, when I remove the $900 automation, and then run Budget Automation, Only the $1200 amount target remains and then $50 is subtracted from Car Expense category to meet the $1200 target with $1300 set aside. that is unexpected because I really want $900 + $1200 saved in total. Maybe I'm misunderstanding the feature and how to have multiple targets.

If there are objections to this suggested design change, I'm interested to hear the opposition.

Thank you! Other than this, I'm really enjoying the Budget Automation.

<!-- gh-comment-id:4643980644 --> @Kennedy242 commented on GitHub (Jun 7, 2026): <img width="370" height="319" alt="Image" src="https://github.com/user-attachments/assets/c836fac9-599c-48ba-b952-ecd5132d8d1f" /> <img width="490" height="276" alt="Image" src="https://github.com/user-attachments/assets/e4869c26-8a10-4904-aa7a-9de19c0e3fd6" /> ## Why must I remove past targets in order for the Budget Automation to run? I have automation so save $900 for my car for June 2026. When I run the automation for July 2026 I get an error that the target month has passed and I must remove that automation to run the Budget Automation. Why? I feel like if the target month has passed, no more money would be set aside for that target. I think the design should be changed so that if target has passed that automation will just do nothing, not error. ( maybe provide a warning or info? ) > When Check Template is run, they report as all passed, it seems that either the same error should show up in Check Template or that Budget Automation should run? > Also in this example. I have $1300 in Car Expense Category, when I remove the $900 automation, and then run Budget Automation, Only the $1200 amount target remains and then $50 is subtracted from Car Expense category to meet the $1200 target with $1300 set aside. that is unexpected because I really want $900 + $1200 saved in total. Maybe I'm misunderstanding the feature and how to have multiple targets. If there are objections to this suggested design change, I'm interested to hear the opposition. Thank you! Other than this, I'm really enjoying the Budget Automation.
Author
Owner

@LadyMongrel commented on GitHub (Jun 8, 2026):

UI can't parse plural but template can

Example is I want to save $60 dollars for new shoes every 2 years. I click to add automation, Save by date 1/1/2027 in this example, Enter Total amount, target month, click repeats, every 2 years.

I click save and hover over the automation icon and it says "Save 60.00 by Jan 2027, reapeating every 1 years.

I can click "Un-Migrate to text notes" and the memo shows Export from automations UI: #template-1 60 by 2027-01 repeat every year

I edit the note saying #template-1 60 by 2027-01 repeat every 2 years

Now i click the automation, it correctly populates Repeats every 2 years, I save it and when i hover over the automation icon it correctly displays "Save 60.00 by Jan 2027, repeating every 2 years"

<!-- gh-comment-id:4653661241 --> @LadyMongrel commented on GitHub (Jun 8, 2026): # UI can't parse plural but template can Example is I want to save $60 dollars for new shoes every 2 years. I click to add automation, Save by date 1/1/2027 in this example, Enter Total amount, target month, click repeats, every 2 years. I click save and hover over the automation icon and it says "Save 60.00 by Jan 2027, reapeating every 1 years. I can click "Un-Migrate to text notes" and the memo shows `Export from automations UI: #template-1 60 by 2027-01 repeat every year` I edit the note saying `#template-1 60 by 2027-01 repeat every 2 years` Now i click the automation, it correctly populates Repeats every 2 years, I save it and when i hover over the automation icon it correctly displays "Save 60.00 by Jan 2027, repeating every 2 years"
Author
Owner

@matt-fidd commented on GitHub (Jun 8, 2026):

UI can't parse plural but template can

Example is I want to save $60 dollars for new shoes every 2 years. I click to add automation, Save by date 1/1/2027 in this example, Enter Total amount, target month, click repeats, every 2 years.

I click save and hover over the automation icon and it says "Save 60.00 by Jan 2027, reapeating every 1 years.

I can click "Un-Migrate to text notes" and the memo shows Export from automations UI: #template-1 60 by 2027-01 repeat every year

I edit the note saying #template-1 60 by 2027-01 repeat every 2 years

Now i click the automation, it correctly populates Repeats every 2 years, I save it and when i hover over the automation icon it correctly displays "Save 60.00 by Jan 2027, repeating every 2 years"

Hi, you should be able to change the repetition period in the UI

Image
<!-- gh-comment-id:4653675176 --> @matt-fidd commented on GitHub (Jun 8, 2026): > # UI can't parse plural but template can > Example is I want to save $60 dollars for new shoes every 2 years. I click to add automation, Save by date 1/1/2027 in this example, Enter Total amount, target month, click repeats, every 2 years. > > I click save and hover over the automation icon and it says "Save 60.00 by Jan 2027, reapeating every 1 years. > > I can click "Un-Migrate to text notes" and the memo shows `Export from automations UI: #template-1 60 by 2027-01 repeat every year` > > I edit the note saying `#template-1 60 by 2027-01 repeat every 2 years` > > Now i click the automation, it correctly populates Repeats every 2 years, I save it and when i hover over the automation icon it correctly displays "Save 60.00 by Jan 2027, repeating every 2 years" Hi, you should be able to change the repetition period in the UI <img width="631" height="530" alt="Image" src="https://github.com/user-attachments/assets/cc10f41e-7a20-4ff4-b0f9-c77d2003ea7f" />
Author
Owner

@LadyMongrel commented on GitHub (Jun 9, 2026):

UI can't parse plural but template can

Example is I want to save $60 dollars for new shoes every 2 years. I click to add automation, Save by date 1/1/2027 in this example, Enter Total amount, target month, click repeats, every 2 years.
I click save and hover over the automation icon and it says "Save 60.00 by Jan 2027, reapeating every 1 years.
I can click "Un-Migrate to text notes" and the memo shows Export from automations UI: #template-1 60 by 2027-01 repeat every year
I edit the note saying #template-1 60 by 2027-01 repeat every 2 years
Now i click the automation, it correctly populates Repeats every 2 years, I save it and when i hover over the automation icon it correctly displays "Save 60.00 by Jan 2027, repeating every 2 years"

Hi, you should be able to change the repetition period in the UI
Image

I think i figured it out. I was clicking the arrow buttons moving up the years and hit save and it didn't seem to register. If I type in the box the number 2 it updates.

<!-- gh-comment-id:4660123033 --> @LadyMongrel commented on GitHub (Jun 9, 2026): > > # UI can't parse plural but template can > > Example is I want to save $60 dollars for new shoes every 2 years. I click to add automation, Save by date 1/1/2027 in this example, Enter Total amount, target month, click repeats, every 2 years. > > I click save and hover over the automation icon and it says "Save 60.00 by Jan 2027, reapeating every 1 years. > > I can click "Un-Migrate to text notes" and the memo shows `Export from automations UI: #template-1 60 by 2027-01 repeat every year` > > I edit the note saying `#template-1 60 by 2027-01 repeat every 2 years` > > Now i click the automation, it correctly populates Repeats every 2 years, I save it and when i hover over the automation icon it correctly displays "Save 60.00 by Jan 2027, repeating every 2 years" > > Hi, you should be able to change the repetition period in the UI > <img alt="Image" width="631" height="530" src="https://private-user-images.githubusercontent.com/81489167/604704799-cc10f41e-7a20-4ff4-b0f9-c77d2003ea7f.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODEwMTEwODQsIm5iZiI6MTc4MTAxMDc4NCwicGF0aCI6Ii84MTQ4OTE2Ny82MDQ3MDQ3OTktY2MxMGY0MWUtN2EyMC00ZmY0LWIwZjktYzc3ZDIwMDNlYTdmLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjA2MDklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwNjA5VDEzMTMwNFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWJiOTBlYTJkZjVhMjEyNjllYjgwMjE0NGY5NDFmM2U3ZTRmYjk5ZGE1ZDkxYmU3NDBmOWQwN2Q1NGQ3YjlkY2EmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JnJlc3BvbnNlLWNvbnRlbnQtdHlwZT1pbWFnZSUyRnBuZyJ9.oq8qmO-Lc057OnW-ytI-Z-d3-wytuagCGhDS_3SkT34"> I think i figured it out. I was clicking the arrow buttons moving up the years and hit save and it didn't seem to register. If I type in the box the number 2 it updates.
Author
Owner

@stevedionysopolos commented on GitHub (Jun 9, 2026):

Automation UI flickering

It look's like the automation UI is stuck in a loading loop as soon as I open it. I am still able to exit it with ESC, tho.

Expand to view recording Image

System information:
OS Name Microsoft Windows 11 Pro
Version 10.0.26200 Build 26200
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DESKTOP-135U4Q5
System Manufacturer ASUS
System Model System Product Name
System Type x64-based PC
System SKU SKU
Processor AMD Ryzen 7 5700X 8-Core Processor, 3401 Mhz, 8 Core(s), 16 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 3607, 22.03.2024
SMBIOS Version 3.3
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer ASUSTeK COMPUTER INC.
BaseBoard Product TUF GAMING B550-PLUS WIFI II
BaseBoard Version Rev X.0x
Platform Role Desktop
Secure Boot State On
PCR7 Configuration Elevation Required to View
Windows Directory C:\WINDOWS
System Directory C:\WINDOWS\system32
Boot Device \Device\HarddiskVolume1
Locale United Kingdom
Hardware Abstraction Layer Version = "10.0.26100.1"
User Name DESKTOP-135U4Q5\Stephan
Time Zone W. Europe Daylight Time
Installed Physical Memory (RAM) 32.0 GB
Total Physical Memory 31.9 GB
Available Physical Memory 24.4 GB
Total Virtual Memory 33.9 GB
Available Virtual Memory 25.1 GB
Page File Space 2.00 GB
Page File C:\pagefile.sys
Kernel DMA Protection Off
Virtualization-based security Not enabled
App Control for Business policy Enforced
App Control for Business user mode policy Off
Automatic Device Encryption Support Elevation Required to View
Hyper-V - VM Monitor Mode Extensions Yes
Hyper-V - Second Level Address Translation Extensions Yes
Hyper-V - Virtualization Enabled in Firmware No
Hyper-V - Data Execution Protection Yes

<!-- gh-comment-id:4662985805 --> @stevedionysopolos commented on GitHub (Jun 9, 2026): # Automation UI flickering It look's like the automation UI is stuck in a loading loop as soon as I open it. I am still able to exit it with ESC, tho. <details> <summary>Expand to view recording</summary> <img width="956" height="758" alt="Image" src="https://github.com/user-attachments/assets/db002910-f865-4239-b701-dcd703fa8723" /> </details> System information: OS Name Microsoft Windows 11 Pro Version 10.0.26200 Build 26200 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name DESKTOP-135U4Q5 System Manufacturer ASUS System Model System Product Name System Type x64-based PC System SKU SKU Processor AMD Ryzen 7 5700X 8-Core Processor, 3401 Mhz, 8 Core(s), 16 Logical Processor(s) BIOS Version/Date American Megatrends Inc. 3607, 22.03.2024 SMBIOS Version 3.3 Embedded Controller Version 255.255 BIOS Mode UEFI BaseBoard Manufacturer ASUSTeK COMPUTER INC. BaseBoard Product TUF GAMING B550-PLUS WIFI II BaseBoard Version Rev X.0x Platform Role Desktop Secure Boot State On PCR7 Configuration Elevation Required to View Windows Directory C:\WINDOWS System Directory C:\WINDOWS\system32 Boot Device \Device\HarddiskVolume1 Locale United Kingdom Hardware Abstraction Layer Version = "10.0.26100.1" User Name DESKTOP-135U4Q5\Stephan Time Zone W. Europe Daylight Time Installed Physical Memory (RAM) 32.0 GB Total Physical Memory 31.9 GB Available Physical Memory 24.4 GB Total Virtual Memory 33.9 GB Available Virtual Memory 25.1 GB Page File Space 2.00 GB Page File C:\pagefile.sys Kernel DMA Protection Off Virtualization-based security Not enabled App Control for Business policy Enforced App Control for Business user mode policy Off Automatic Device Encryption Support Elevation Required to View Hyper-V - VM Monitor Mode Extensions Yes Hyper-V - Second Level Address Translation Extensions Yes Hyper-V - Virtualization Enabled in Firmware No Hyper-V - Data Execution Protection Yes
Author
Owner

@metabubble commented on GitHub (Jun 10, 2026):

Text template conversion incomplete and will not run when fixed manually

#template 32.5 repeat every 1 days starting 2025-02-01 up to 2500

This is migrated without the "up to 2500" portion as such:

Image

If I proceed to add a monthly balance cap of 2500, it saved. But when I run it, I get

There were errors interpreting some templates:
Category: Only one up to allowed per category

<!-- gh-comment-id:4668638675 --> @metabubble commented on GitHub (Jun 10, 2026): Text template conversion incomplete and will not run when fixed manually `#template 32.5 repeat every 1 days starting 2025-02-01 up to 2500` This is migrated without the "up to 2500" portion as such: <img width="942" height="352" alt="Image" src="https://github.com/user-attachments/assets/a04f4e67-e24f-45cd-84a0-7025ed20f0a8" /> If I proceed to add a monthly balance cap of 2500, it saved. But when I run it, I get There were errors interpreting some templates: Category: Only one `up to` allowed per category
Author
Owner

@lionirdeadman commented on GitHub (Jun 10, 2026):

There's a few nice things that would be nice to have along with this feature, I believe:

  • The ability to budget up-to-the-goal by right-clicking the balance when it is yellow or red which would be a pretty similar interaction as to when you cover overspending in a category;
  • The ability to select multiple categories to see the difference between the goal and budgeted amounts which would help plan during the month (this could also be expanded later to see things like budgeted amounts, overfunded categories or such things);
  • The month header could include the goals total, it feels like the design would be well suited here.

This is something that may be more controversial but it's something I had grown accustomed to while using nYNAB:

  • The ability to ignore a specific goal during a month, which would have the effect of keeping the balance number green.

While this might lead to forgetting that it wasn't fully funded, it does help to have a less noisy view of your budget when you know a specific category will have no spending and/or no funded for that month.

Hope this is the correct place for this feedback.

<!-- gh-comment-id:4675542250 --> @lionirdeadman commented on GitHub (Jun 10, 2026): There's a few nice things that would be nice to have along with this feature, I believe: - The ability to budget up-to-the-goal by right-clicking the balance when it is yellow or red which would be a pretty similar interaction as to when you cover overspending in a category; - The ability to select multiple categories to see the difference between the goal and budgeted amounts which would help plan during the month (this could also be expanded later to see things like budgeted amounts, overfunded categories or such things); - The month header could include the goals total, it feels like the design would be well suited here. This is something that may be more controversial but it's something I had grown accustomed to while using nYNAB: - The ability to ignore a specific goal during a month, which would have the effect of keeping the balance number green. While this might lead to forgetting that it wasn't fully funded, it does help to have a less noisy view of your budget when you know a specific category will have no spending and/or no funded for that month. Hope this is the correct place for this feedback.
Author
Owner

@kevincam3 commented on GitHub (Jun 11, 2026):

I can't get it to work. When I open it my screen just flickers. I'm on version v26.6.0
https://app.screencast.com/c9dCz7FvP8OTG

<!-- gh-comment-id:4679359119 --> @kevincam3 commented on GitHub (Jun 11, 2026): I can't get it to work. When I open it my screen just flickers. I'm on version v26.6.0 https://app.screencast.com/c9dCz7FvP8OTG
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#117547