mirror of
https://github.com/actualbudget/actual.git
synced 2026-07-15 22:54:03 -05:00
Open
opened 2026-06-11 12:47:01 -05:00 by GiteaMirror
·
85 comments
No Branch/Tag Specified
master
dependabot/npm_and_yarn/npm_and_yarn-cd62b4b37a
enforce-append-only-migrations-ci
claude/error-codes-worker-boundary-26i5uu
api-browser-custom-data-dir
tabedzki/feat/replacing-month-picker-with-day-picker
delay-initial-sync-until-loaded
jfdoming/mobile-app-build
cross-version-sync-compat
jfdoming/api-tokens-part-1
jfdoming/api-tokens-part-2
jfdoming/api-tokens-part-3
jfdoming/mobile-app-updates
claude/budget-version-migration-compat-151jlr
claude/worker-error-serialization-9iqtl7
claude/react-table-library-research-afx83z
claude/issue-8401-regression-test-9nw9l3
jfdoming/mobile-app-foundation-part-1
jfdoming/mobile-app-scaffold
release
ai-fix-cleanup-def-8290
claude/relaxed-shannon-jusywa
claude/fervent-keller-s6f2fq
claude/determined-feynman-st1y9z
claude/wizardly-einstein-vi2wce
claude/sweet-albattani-7nseio
feat/bank-sync-per-budget-file
claude/affectionate-cannon-y0kc82
claude/dependabot-findings-m9pgmb
claude/mac-app-ios-publish-zjs1lz
claude/vigilant-tesla-aiiyos
depot-migrate-secrets-1781296330308
claude/quirky-cerf-v5qck7
claude/animation-removal-alternative-2etfh1
claude/netlify-preview-comments-consolidate-9XPYa
osc/7391-error-boundaries-reports
claude/pensive-dijkstra-7DYui
claude/server-app-version-mismatch-HTCGv
claude/pr-8027-review-feedback-mELuO
claude/zealous-wozniak-e5pO0
claude/intelligent-heisenberg-BSHJq
claude/translation-download-refactor-jFRsO
claude/mobile-performance-ideas-G9PAO
claude/github-issue-7988-5A5ly
blacksmith-migration-ff70d2d
claude/great-mayer-KRvOk
claude/react-native-ios-compilation-fcJh5
claude/serene-goldberg-58xv0
claude/kind-euler-LVG3K
release-automation/edge-nightly
7710-bundle-migrations
claude/fix-docker-build-error-WMfed
claude/llm-compatible-release-notes-t20Nr
7710-tests-tdd
cursor/transaction-table-rewrite-f077
claude/plan-ci-secure-context-OtEe1
claude/fix-issue-7667-DPXi3
cursor/resolve-pr-7449-ee11
claude/fix-typescript-build-error-JPtZ5
copilot/add-repository-configs-to-packages
worktree-compressed-drifting-ritchie
claude/api-consumer-verification-kfz1K
pr-7454
claude/fix-issue-7410-LLLQ4
revert-7281-generate-icons
react-query-useSchedules
copilot/sub-pr-6140
package-upgrades
v26.7.0
v26.6.0
v26.5.2
v26.5.1
v26.5.0
v26.4.0
v26.3.0
v26.2.1
v26.2.0
v26.1.0
v25.12.0
v25.11.0
v25.10.0
v25.9.0
v25.8.0
v25.7.1
v25.7.0
v25.6.1
v25.6.0
v25.5.0
v25.4.0
v25.3.1
v25.3.0
v25.2.1
v25.2.0
v25.1.0
v24.12.0
v24.11.0
v24.10.1
v24.10.0
v24.9.0
v24.8.0
v24.7.0
v24.6.0
v24.5.0
v24.4.0
v24.3.0
v24.2.0
v24.1.0
v23.12.0
v23.11.0
v23.10.0
v23.9.0
v23.8.1
v23.8.0
v23.7.2
v23.7.1
v23.7.0
v23.6.0
v23.5.0
v23.4.2
v23.4.1
v23.4.0
v23.3.2
v23.3.0
v23.2.9
v23.2.5
v23.1.12
v22.12.9
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
Mirrored from GitHub Pull Request
No Label
feedback
Milestone
No items
No Milestone
Projects
Clear projects
No project
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#117547
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @matt-fidd on GitHub (May 3, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/7692
@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.
@youngcw commented on GitHub (May 4, 2026):
Maybe cleanup templates should get ignored for now instead of causing an error.
@matt-fidd commented on GitHub (May 4, 2026):
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.
#goaldirectives need some real thinking about, I've still not worked out a good way to support them@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
@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:
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:
@Juulz commented on GitHub (May 4, 2026):
My thought is that they are an
up totemplate 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 anup totemplate can have a checkbox to indicate if this is a goal? Only oneup toper anyway, so this would work.@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.
@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.
The **really** interesting thing is that they all budget the correct amount when the button is pressed!
@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.
@matt-fidd commented on GitHub (May 11, 2026):
This is something we've been looking at adding as a stage here, something like the below?
@matt-fidd commented on GitHub (May 11, 2026):
I'd put money on this being a priority based issue. The first couple of screenshots show priority
0, with the others showing150. 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.
@Juulz commented on GitHub (May 11, 2026):
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.
@Juulz commented on GitHub (May 11, 2026):
Yes! Except, order within a group DOES matter!
@matt-fidd commented on GitHub (May 11, 2026):
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.
@Juulz commented on GitHub (May 11, 2026):
Yes, it works great. The tooltip explains it well, also. 💯
@totallynotjon commented on GitHub (May 11, 2026):
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.
@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.
@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
@matt-fidd commented on GitHub (May 12, 2026):
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
goaldirectives, 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/7792Good catch! Thank you. Addressed in https://github.com/actualbudget/actual/pull/7810
@iceita78 commented on GitHub (May 12, 2026):
Hi Matt, ok thank you for the info and it's my pleasure in helping you with testing!
@Juulz commented on GitHub (May 12, 2026):
Please change pageTextSubdued to pageTextLight. I think subdued should only be used for disabled text.
@matt-fidd commented on GitHub (May 12, 2026):
Good call! https://github.com/actualbudget/actual/pull/7819 :)
@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.
Also, The balance cap is now "below".
@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%}]@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.
@Juulz commented on GitHub (May 13, 2026):
If this is implemented, it would be cool to show the note(s) when you hover the clock icon.
@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?
@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.
@matt-fidd commented on GitHub (May 13, 2026):
@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!
@totallynotjon great catch, thank you for reporting, that should be fixed in the PR above too
@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 Xline 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.
@matt-fidd commented on GitHub (May 13, 2026):
Agreed, but it's currently acting as if it was
#template up to xby adding a refill automation@youngcw commented on GitHub (May 13, 2026):
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.
@matt-fidd commented on GitHub (May 13, 2026):
It's kind of a weird edge case, because you'd almost always be better off just tacking
up to xon 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@totallynotjon commented on GitHub (May 13, 2026):
@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.
@matt-fidd commented on GitHub (May 17, 2026):
Done! https://github.com/actualbudget/actual/pull/7881
@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.
@Juulz commented on GitHub (May 20, 2026):
Will we always allow notes #templates to function or will we turn them off at a point?
@matt-fidd commented on GitHub (May 20, 2026):
I plan to phase them out when the UI is proven
@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.
@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.
Would expect something closer to the +/- options like in the rules editor.

@matt-fidd commented on GitHub (May 21, 2026):
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.
@mnil commented on GitHub (May 21, 2026):
@matt-fidd I thought it would be neat with sorting the schedules so created a PR:
@matt-fidd commented on GitHub (May 21, 2026):
Amazing, thank you!
@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.
@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.
@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.
Perhaps an idea to also allow Completed schedules in Budget automation so when re-activated, they will work?
@youngcw commented on GitHub (Jun 1, 2026):
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?
@Juulz commented on GitHub (Jun 1, 2026):
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.
@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.
@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:
Or in the comment when hovering over the pie-chart-symbol?
@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)
@Juulz commented on GitHub (Jun 2, 2026):
I was able to reproduce this. Thread on discord: https://discord.com/channels/937901803608096828/1511363890343182396
@matt-fidd 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.
@iceita78 commented on GitHub (Jun 2, 2026):
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
@Juulz commented on GitHub (Jun 2, 2026):
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.
@RedHare-Exe commented on GitHub (Jun 2, 2026):
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:
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!
@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.
@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.
@YEGCSharpDev commented on GitHub (Jun 3, 2026):
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.
@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
nightlyrelease, 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.@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:
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.
@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.
@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:
Different priorities:
@Juulz commented on GitHub (Jun 4, 2026):
There is a warning about this in the docs for Cover schedule and Save by date automations.
@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/
@YEGCSharpDev commented on GitHub (Jun 4, 2026):
Yes! Its good now. I am able to zoom in and zoom out the text doesnt overflow.
@BipolarAnt commented on GitHub (Jun 4, 2026):
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
@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
@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/
@YEGCSharpDev commented on GitHub (Jun 6, 2026):
This works well. I tried doing create and edit workflows. Didn't run into any issues.
@x-rous commented on GitHub (Jun 6, 2026):
Looking good, that's the only off bit I found.
@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
nothingin the space.Clicking "Try Again" resets the display without saving.
Workaround: Simply highlighting the text and replacing with a number without deleting will avoid the error.
@matt-fidd commented on GitHub (Jun 6, 2026):
Thanks for reporting! This was fixed in https://github.com/actualbudget/actual/pull/8082
@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
@matt-fidd commented on GitHub (Jun 6, 2026):
Thanks for reporting, as above this has been fixed in nightly now
@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.
@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:
startingdate is generated asundefinedby default, causing the budgeted amount to drop to zero.undefineddate 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 undefinedon Balance Cap$50 every week starting 2026-01-01#template-1 50 repeat every 1 weeks starting 2026-01-01#template O up to 85 per week starting undefinedWorkaround: 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 undefinedtostarting 2026-06-07.Bug 2 - Balance Cap starting date defaults to corresponding day of day of the week in current week, not the automation's starting date
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-07Because the balance cap's starting date is
2026-06-07(today) rather than2026-01-01(the automation's starting date), the cap does not apply to any months prior to June 2026.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:
starting 2026-06-07→starting 2026-01-01.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 0line. Re-migrating back to UI automations then creates a duplicate second automation with a value of zero, corrupting the configuration.#template 0line representing the balance cap :$0, in addition to the original Fixed Amount automation.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
#template 0line.$0automation being added alongside the original.@Kennedy242 commented on GitHub (Jun 7, 2026):
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? )
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.
@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 yearI edit the note saying
#template-1 60 by 2027-01 repeat every 2 yearsNow 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"
@matt-fidd commented on GitHub (Jun 8, 2026):
Hi, you should be able to change the repetition period in the UI
@LadyMongrel commented on GitHub (Jun 9, 2026):
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.
@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
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
@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 2500This is migrated without the "up to 2500" portion as such:
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 toallowed per category@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:
This is something that may be more controversial but it's something I had grown accustomed to while using nYNAB:
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.
@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