mirror of
https://github.com/actualbudget/actual.git
synced 2026-03-11 20:44:32 -05:00
[Bug]: Inconsistent Weekly Transactions #2122
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/actual#2122
Reference in New Issue
Block 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 @TimPasquini on GitHub (May 12, 2025).
Verified issue does not already exist?
What happened?
I get paid weekly and have several scheduled transactions set to auto-post fixed amounts. I've created a weekly schedule for these, but when I reconcile at the end of the month, usually only one or two transactions out of an expected 4 or 5 have posted.
The schedule view shows upcoming transactions as expected, but by the next reconciliation I perform, only the first of those has posted. The others have disappeared from both the schedule display and the ledger entirely.
Each month I re-enter the missing transactions manually and reassign them to the schedule. This seems to reset the schedule into a working state, allowing one new transaction to post before the issue reoccurs.
I've investigated the repo a bit, though I really only know Python and had to rely on LLMs for help with syntax. I suspect the problem lies with the
next_datenot advancing correctly. This would explain why after a manual intervention I get one successful post, as linking transactions likely causes a successful update to thenext_date, but then it makes an automatic posting, fails the process on that end, and the failure loop restarts.I had mentioned in issue #4705, using "Post Transaction Today" duplicated the last transaction instead of posting the upcoming one. The linked commit 91c0eb5 fixed the issue by moving from
next_datetocurrent_date, so this supports my suspicion thatnext_dateis failing to advance.I’d like to gather more evidence to try and narrow down the failure, but the Docker implementation seems to setup logging at the
infolevel by default, and I’m unsure how to increase the log verbosity. I have the docker implemented through UnRaid.I also feel I should mention that all of my monthly scheduled transactions seem to work fine, this issue seems to be specifically tied to weekly schedules.
How can we reproduce the issue?
I don't think I'm doing anything abnormal in setting things up, so I'd suggest creating a weekly schedule with auto-posting turned on. Allow it to progress through a month with no interventions, and then look to see if any are missing.
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Firefox
Operating System
Linux
@TimPasquini commented on GitHub (Jun 1, 2025):
This appears to be fixed in 0.25.5 and I probably jumped the gun posting the issue (to be fair, this hadn't been working for a long time for me).
I was on 0.25.5 when I posted, but at that point only a week had passed by. As part of debugging and writing up my issue I rebuilt my weekly schedules and it appears that I finally have transactions showing on the ledger for the past several weeks.
I'm guessing that the fix on the
next_datevscurrent_datechanges related to #4705 fixed this issue.@TimPasquini commented on GitHub (Aug 2, 2025):
Ok, I guess I need to reopen this because weekly transactions are absolutely not working. I left actual alone for 2 months without any interaction except updates. I have at least 3 rules that should post transactions weekly, but here is a sample of what actually posted:
and here is the rule:
Based on my understanding of how I set this up, every single week on Wednesday there should have been a posted, but not reconciled, transaction for $50 being transferred.
The same issue seems to exist for my other weekly schedules.