github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-03-09 19:52:56 -05:00
Code Issues 250 Packages Projects Releases 53 Wiki Activity

[Bug]: Posting scheduled transaction before the due-date does not cause schedule to be paid #2762

New Issue
Closed
opened 2026-02-28 20:27:01 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-02-28 20:27:01 -06:00
Owner
Copy Link

Originally created by @majkrzak on GitHub (Jan 2, 2026).

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

When posting recurring transaction which due-date is in the future, schedule is not marked as paid. Instead it is still displayed as "Upcoming". Only posting on, or after due-date makes it "Paid".

How can we reproduce the issue?

How can we reproduce the issue?

Image Image

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Firefox

Operating System

Linux

Originally created by @majkrzak on GitHub (Jan 2, 2026). ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? When posting recurring transaction which due-date is in the future, schedule is not marked as paid. Instead it is still displayed as "Upcoming". Only posting on, or after due-date makes it "Paid". ### How can we reproduce the issue? How can we reproduce the issue? <img width="721" height="644" alt="Image" src="https://github.com/user-attachments/assets/50ef7373-e49d-47a3-89ec-d383f56ea032" /> <img width="1245" height="115" alt="Image" src="https://github.com/user-attachments/assets/177ae50a-08dd-4d96-a891-03d5c23836b1" /> ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Firefox ### Operating System Linux
GiteaMirror added the bug label 2026-02-28 20:27:02 -06:00
GiteaMirror commented 2026-02-28 20:27:03 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Jan 5, 2026):

You are outside of the matching window. Manually skip the next instance.

@youngcw commented on GitHub (Jan 5, 2026): You are outside of the matching window. Manually skip the next instance.
GiteaMirror commented 2026-02-28 20:27:03 -06:00
Author
Owner
Copy Link

@majkrzak commented on GitHub (Jan 5, 2026):

@youngcw can you elaborate a bit?

What the matching window?
It seems to be hard-coded as 2, but I had not find exactly where. I guess it can be done a bit smarter and take in account more variables, like the actual starting date of the schedule, etc. I may have time to implement it.

Skipping the next one does not look like a permanent solution. Next month, if paid before the 2 days window will cause the problem again.

@majkrzak commented on GitHub (Jan 5, 2026): @youngcw can you elaborate a bit? What the matching window? It seems to be hard-coded as 2, but I had not find exactly where. I guess it can be done a bit smarter and take in account more variables, like the actual starting date of the schedule, etc. I may have time to implement it. Skipping the next one does not look like a permanent solution. Next month, if paid before the 2 days window will cause the problem again.
GiteaMirror commented 2026-02-28 20:27:03 -06:00
Author
Owner
Copy Link

@youngcw commented on GitHub (Jan 5, 2026):

I think the schedule matching window is +- 3 days

@youngcw commented on GitHub (Jan 5, 2026): I think the schedule matching window is +- 3 days
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
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#2762
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?