github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-05 22:52:20 -05:00
Code Issues 1.5k Packages Projects Releases 54 Wiki Activity

[GH-ISSUE #2851] [Bug]: Weekly Schedules getting stuck as Paid #42795

New Issue
Closed
opened 2026-04-26 02:54:12 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-26 02:54:12 -05:00
Owner
Copy Link

Originally created by @Teprifer on GitHub (Jun 7, 2024).
Original GitHub issue: https://github.com/actualbudget/actual/issues/2851

Verified issue does not already exist?

  • I have searched and found no existing issue
  • I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file)

What happened?

Noticed x3 weekly schedules a few weeks ago got stuck as 'Paid' and stopped auto-adding transactions each week. I'd been posting these manually with investigation on my 'get around to it list' but saw someone else with this issue in discord so finally gotten around to making the bug report. Reach out if further details are required.

Example of one:
image
image

Changing settings of this didn't get it un-stuck.

Following a similar report in discord ( https://discord.com/channels/937901803608096828/969693280226906162/1248406393493389322 )

Carson: has anyone had a schedule get "off" by a period? i have a weekly-on-monday schedule, the last of which was on June 3rd. with the transaction on June 3rd, the June 10th iteration shows as "paid" already (even though it shows as an upcoming instance in the schedules menu), and doesn't appear as upcoming. if i manually change the June 3rd transaction to June 2nd, the one on the 10th all of a sudden kicks in and shows as upcoming. changing the existing transaction back to the 3rd makes it go away again. it seems like it's taking that transaction as the one that's supposed to happen next week 😮

I amended the date of the most recent transaction to be 1 day different, and now the schedule shows as Upcoming again.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Firefox, Chrome

Operating System

Windows 11

Originally created by @Teprifer on GitHub (Jun 7, 2024). Original GitHub issue: https://github.com/actualbudget/actual/issues/2851 ### Verified issue does not already exist? - [X] I have searched and found no existing issue - [X] I will be providing steps how to reproduce the bug (in most cases this will also mean uploading a demo budget file) ### What happened? Noticed x3 weekly schedules a few weeks ago got stuck as 'Paid' and stopped auto-adding transactions each week. I'd been posting these manually with investigation on my 'get around to it list' but saw someone else with this issue in discord so finally gotten around to making the bug report. Reach out if further details are required. Example of one: ![image](https://github.com/actualbudget/actual/assets/34882928/1f50e551-a4c7-430c-b3ff-1217741ab1ed) ![image](https://github.com/actualbudget/actual/assets/34882928/b73a0291-5859-4607-b202-1f4817748fc9) Changing settings of this didn't get it un-stuck. Following a similar report in discord ( https://discord.com/channels/937901803608096828/969693280226906162/1248406393493389322 ) > Carson: has anyone had a schedule get "off" by a period? i have a weekly-on-monday schedule, the last of which was on June 3rd. with the transaction on June 3rd, the June 10th iteration shows as "paid" already (even though it shows as an upcoming instance in the schedules menu), and doesn't appear as upcoming. if i manually change the June 3rd transaction to June 2nd, the one on the 10th all of a sudden kicks in and shows as upcoming. changing the existing transaction back to the 3rd makes it go away again. it seems like it's taking that transaction as the one that's supposed to happen next week 😮 I amended the date of the most recent transaction to be 1 day different, and now the schedule shows as Upcoming again. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Firefox, Chrome ### Operating System Windows 11
GiteaMirror added the regressionbug labels 2026-04-26 02:54:12 -05:00
GiteaMirror commented 2026-04-26 02:54:14 -05:00
Author
Owner
Copy Link

@CarsonHoffman commented on GitHub (Jun 7, 2024):

From a bisect, this seems to have been introduced in b0f55fae38. Looking at the 7 in the diff, it seems fairly obvious what's going on, though I'm not entirely sure what the best course of action is going forward, as I'm not familiar with what this was attempting to fix. @joel-jeremy do you have any thoughts?

<!-- gh-comment-id:2155496640 --> @CarsonHoffman commented on GitHub (Jun 7, 2024): From a bisect, this seems to have been introduced in b0f55fae383f8e2ee3847229644791d70c62d88e. Looking at the 7 in the diff, it seems fairly obvious what's going on, though I'm not entirely sure what the best course of action is going forward, as I'm not familiar with what this was attempting to fix. @joel-jeremy do you have any thoughts?
GiteaMirror commented 2026-04-26 02:54:14 -05:00
Author
Owner
Copy Link

@Teprifer commented on GitHub (Jun 11, 2024):

Confirmed exporting a file from 24.6 and rolling back to 24.5 is a workaround that can be used until this is fixed.

<!-- gh-comment-id:2159816326 --> @Teprifer commented on GitHub (Jun 11, 2024): Confirmed exporting a file from 24.6 and rolling back to 24.5 is a workaround that can be used until this is fixed.
GiteaMirror commented 2026-04-26 02:54:15 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Jun 16, 2024):

cc @joel-jeremy any objections to reverting #2712 ? I think getting weekly schedules up-and-running again would take prio over the edge-case patch in 2712.

<!-- gh-comment-id:2171777824 --> @MatissJanis commented on GitHub (Jun 16, 2024): cc @joel-jeremy any objections to reverting #2712 ? I think getting weekly schedules up-and-running again would take prio over the edge-case patch in 2712.
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
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug regression
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#42795
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?