github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-15 22:54:03 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #6160] [Bug]: Schedule rule action templating causes fatal error #92256

New Issue
Closed
opened 2026-05-26 03:08:43 -05:00 by GiteaMirror · 5 comments
GiteaMirror commented 2026-05-26 03:08:43 -05:00
Owner
Copy Link

Originally created by @ntsp00 on GitHub (Nov 16, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/6160

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

I'm using rule action templating to edit monthly schedules. To have the rule dynamically set the date to the last day of each month, I'm using the set date action with the template {{addDays date -1}}. After creating 3 of these schedules for different accounts, everything appears fine and the schedules function as intended. However, after creating a 4th schedule, navigating to 'All accounts' or the specific account the 4th schedule was created for causes a fatal error until that schedule is deleted. One time while troubleshooting this error it didn't happen on the 4th schedule, but did happen on the 5th.

Image Image Image

How can we reproduce the issue?

Create 4-5 monthly schedules and use rule action templating to set the date with the template {{addDays date -1}}.

Note: Hosting Actual in a Proxmox LXC and currently on v25.11.0.

Where are you hosting Actual?

Other

What browsers are you seeing the problem on?

Firefox

Operating System

Windows 11

Originally created by @ntsp00 on GitHub (Nov 16, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/6160 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? I'm using rule action templating to edit monthly schedules. To have the rule dynamically set the date to the last day of each month, I'm using the `set date` action with the template `{{addDays date -1}}`. After creating 3 of these schedules for different accounts, everything appears fine and the schedules function as intended. However, after creating a 4th schedule, navigating to 'All accounts' or the specific account the 4th schedule was created for causes a fatal error until that schedule is deleted. One time while troubleshooting this error it didn't happen on the 4th schedule, but did happen on the 5th. <img width="1265" height="774" alt="Image" src="https://github.com/user-attachments/assets/9f3c8c44-0990-47ec-aeca-e20d48cb0f7b" /> <img width="1256" height="886" alt="Image" src="https://github.com/user-attachments/assets/2b3fd60a-ceb1-40b8-a7ce-d303d0c3ea36" /> <img width="932" height="696" alt="Image" src="https://github.com/user-attachments/assets/203e6615-c504-4b7d-8683-d9269fd14fa9" /> ### How can we reproduce the issue? Create 4-5 monthly schedules and use rule action templating to set the date with the template `{{addDays date -1}}`. Note: Hosting Actual in a Proxmox LXC and currently on v25.11.0. ### Where are you hosting Actual? Other ### What browsers are you seeing the problem on? Firefox ### Operating System Windows 11
GiteaMirror added the rulesbugcan’t replicate labels 2026-05-26 03:08:44 -05:00
GiteaMirror commented 2026-05-26 03:08:50 -05:00
Author
Owner
Copy Link

@ntsp00 commented on GitHub (Nov 16, 2025):

Error message:

T_e@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:58:88261 ws@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:58:87513 BD@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:1023:79617 @https://192.168.1.56:5006/static/js/index.DPLTB89t.js:1025:15440 cR@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:57:53846 useState@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:57:62042 E5e/vn.useState@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:18:7538 uTe<@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:1025:15425 rR@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:57:48915 ER@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:57:71846 VU@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:57:69246 HU@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:57:68794 tH@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:57:84733 _H@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:57:118321 XCe@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:57:117351 VR@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:57:117177 CH@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:57:113931 HH@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:57:125913 _@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:34:1582
<!-- gh-comment-id:3537367765 --> @ntsp00 commented on GitHub (Nov 16, 2025): Error message: ```` T_e@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:58:88261 ws@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:58:87513 BD@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:1023:79617 @https://192.168.1.56:5006/static/js/index.DPLTB89t.js:1025:15440 cR@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:57:53846 useState@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:57:62042 E5e/vn.useState@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:18:7538 uTe<@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:1025:15425 rR@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:57:48915 ER@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:57:71846 VU@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:57:69246 HU@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:57:68794 tH@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:57:84733 _H@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:57:118321 XCe@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:57:117351 VR@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:57:117177 CH@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:57:113931 HH@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:57:125913 _@https://192.168.1.56:5006/static/js/index.DPLTB89t.js:34:1582 ````
GiteaMirror commented 2026-05-26 03:08:50 -05:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Nov 17, 2025):

Could you provide a sample budget file with the schedules already set up to more easily recreate this?

<!-- gh-comment-id:3539629826 --> @matt-fidd commented on GitHub (Nov 17, 2025): Could you provide a sample budget file with the schedules already set up to more easily recreate this?
GiteaMirror commented 2026-05-26 03:08:51 -05:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Nov 17, 2025):

Also, if you're just wanting the rule to match the end of the month, you can do that through "add specific days" in the schedule edit modal.

<!-- gh-comment-id:3539630492 --> @matt-fidd commented on GitHub (Nov 17, 2025): Also, if you're just wanting the rule to match the end of the month, you can do that through "add specific days" in the schedule edit modal.
GiteaMirror commented 2026-05-26 03:08:53 -05:00
Author
Owner
Copy Link

@ntsp00 commented on GitHub (Nov 17, 2025):

Could you provide a sample budget file with the schedules already set up to more easily recreate this?

I deleted all of the schedules after opening this issue so I went just now to recreate them in order to trigger the fatal error. Now they all work and no matter how many schedules I create, I can't get the error to happen again! I guess that's good news, but I do feel a little crazy now lol. If it ever happens again, I'll be sure to export timely so I'm not wasting your time.

Also, if you're just wanting the rule to match the end of the month, you can do that through "add specific days" in the schedule edit modal.

Ah, thanks for pointing it out! I checked there but I must have overlooked it with how it's formatted:

Image

It might be useful to have a 'Last Day' button here instead or in addition, but of course that's a topic for another day 🙂

Image
<!-- gh-comment-id:3544322990 --> @ntsp00 commented on GitHub (Nov 17, 2025): > Could you provide a sample budget file with the schedules already set up to more easily recreate this? I deleted all of the schedules after opening this issue so I went just now to recreate them in order to trigger the fatal error. Now they all work and no matter how many schedules I create, I can't get the error to happen again! I guess that's good news, but I do feel a little crazy now lol. If it ever happens again, I'll be sure to export timely so I'm not wasting your time. > Also, if you're just wanting the rule to match the end of the month, you can do that through "add specific days" in the schedule edit modal. Ah, thanks for pointing it out! I checked there but I must have overlooked it with how it's formatted: <img width="1449" height="1292" alt="Image" src="https://github.com/user-attachments/assets/68fcfae7-50a6-4ad3-ba9e-81d74a96ceea" /> It might be useful to have a 'Last Day' button here instead or in addition, but of course that's a topic for another day 🙂 <img width="753" height="650" alt="Image" src="https://github.com/user-attachments/assets/7a57bf72-baaa-450d-8621-454ff9de12f8" />
GiteaMirror commented 2026-05-26 03:08:55 -05:00
Author
Owner
Copy Link

@matt-fidd commented on GitHub (Nov 18, 2025):

No problem, glad it's working for you now :)

<!-- gh-comment-id:3544423702 --> @matt-fidd commented on GitHub (Nov 18, 2025): No problem, glad it's working for you now :)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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
Mirrored from GitHub 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
No Label bug can’t replicate rules
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#92256
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?