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

[GH-ISSUE #4981] [Bug]: Inconsistent Weekly Transactions #27914

New Issue
Open
opened 2026-04-18 04:30:45 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-18 04:30:45 -05:00
Owner
Copy Link

Originally created by @TimPasquini on GitHub (May 12, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/4981

Verified issue does not already exist?

  • I have searched and found no existing issue

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_date not advancing correctly. This would explain why after a manual intervention I get one successful post, as linking transactions likely causes a successful update to the next_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_date to current_date, so this supports my suspicion that next_date is 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 info level 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

Originally created by @TimPasquini on GitHub (May 12, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/4981 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### 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_date` not advancing correctly. This would explain why after a manual intervention I get one successful post, as linking transactions likely causes a successful update to the `next_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](https://github.com/actualbudget/actual/issues/4705), using "Post Transaction Today" duplicated the last transaction instead of posting the upcoming one. The linked commit [91c0eb5](https://github.com/Bhautik2902/actual/commit/91c0eb51e7ec72be367a06fe938c628126570f1a) fixed the issue by moving from `next_date` to `current_date`, so this supports my suspicion that `next_date` is 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 `info` level 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
GiteaMirror added the bug label 2026-04-18 04:30:45 -05:00
GiteaMirror commented 2026-04-18 04:30:47 -05:00
Author
Owner
Copy Link

@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_date vs current_date changes related to #4705 fixed this issue.

<!-- gh-comment-id:2927957035 --> @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_date` vs `current_date` changes related to #4705 fixed this issue.
GiteaMirror commented 2026-04-18 04:30:48 -05:00
Author
Owner
Copy Link

@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:

Image

and here is the rule:

Image

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.

<!-- gh-comment-id:3146711082 --> @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: <img width="1135" height="208" alt="Image" src="https://github.com/user-attachments/assets/70d62549-f079-47fd-a19e-631b26ebafdc" /> and here is the rule: <img width="832" height="877" alt="Image" src="https://github.com/user-attachments/assets/117ecacc-eabb-4199-83d4-ff2cc5800f3a" /> 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.
GiteaMirror commented 2026-04-18 04:30:50 -05:00
Author
Owner
Copy Link

@anoff commented on GitHub (Mar 22, 2026):

Same issue here, although with daily schedules.

Edit: Checked the codebase a little and might have found the reason - however it does not explain OPs issue - so I created a separate ticket for my issue with daily schedules: #7258

<!-- gh-comment-id:4105075238 --> @anoff commented on GitHub (Mar 22, 2026): Same issue here, although with daily schedules. Edit: Checked the codebase a little and might have found the reason - however it does not explain OPs issue - so I created a separate ticket for my issue with daily schedules: #7258
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
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#27914
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?