github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-07 04:18:51 -05:00
Code Issues 1.6k Packages Projects Releases 55 Wiki Activity

[GH-ISSUE #6244] [Bug]: Posting multiple upcoming transactions for the same schedule within the same upcoming periods uses the first upcoming date #28445

New Issue
Open
opened 2026-04-18 05:12:20 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-18 05:12:20 -05:00
Owner
Copy Link

Originally created by @tabedzki on GitHub (Nov 25, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/6244

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

When using the Schedule feature, the user cannot post a future transaction. For example, if the user has multiple transaction upcoming in the schedule, regardless if the next calendar one is posted, any attempts to post the transaction for a scheduled component before then will result in the first upcoming transaction being posted.

Example, Weekly scheduled payment occurs to give 100 into an account:
If the user's upcoming transaction is scheduled for DAY+2, DAY+9, DAY+16 (doable if we set "upcoming" period to be 1 month), then posting any of those transaction (+2, +9, or +16) will result in the transaction being posted for DAY+2, regardless if DAY+2 was already posted or not.

How can we reproduce the issue?

Define a transaction to occur weekly
Image

Change the period so that multiple schedule payments occur
Image

Starting page for transaction. Home Depot is due today (11/25/2025).
Image

Post today (11/25/2025)'s due transaction.
Image

It posted! Now, go to post the next upcoming transaction (12/02/2025)
Image

Now there are two entries for 11/25/2025 and the upcoming transaction is still there, even though we posted it for (12/02/2025).
Image

Where are you hosting Actual?

None

What browsers are you seeing the problem on?

No response

Operating System

None

Originally created by @tabedzki on GitHub (Nov 25, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/6244 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? When using the Schedule feature, the user cannot post a future transaction. For example, if the user has multiple transaction upcoming in the schedule, regardless if the next calendar one is posted, any attempts to post the transaction for a scheduled component before then will result in the first upcoming transaction being posted. Example, Weekly scheduled payment occurs to give 100 into an account: If the user's upcoming transaction is scheduled for DAY+2, DAY+9, DAY+16 (doable if we set "upcoming" period to be 1 month), then posting any of those transaction (+2, +9, or +16) will result in the transaction being posted for DAY+2, regardless if DAY+2 was already posted or not. ### How can we reproduce the issue? Define a transaction to occur weekly ![Image](https://github.com/user-attachments/assets/b9fe3068-2b4e-41ac-b2d8-463771fdcf6c) Change the period so that multiple schedule payments occur ![Image](https://github.com/user-attachments/assets/f5c636b6-7ad2-4b2d-a3bc-71ba592c6aa6) Starting page for transaction. Home Depot is due today (11/25/2025). ![Image](https://github.com/user-attachments/assets/55b5f4a5-f420-43dc-8296-597caddba824) Post today (11/25/2025)'s due transaction. ![Image](https://github.com/user-attachments/assets/105d7782-5625-44cb-bc4e-a2359b4b65e9) It posted! Now, go to post the next upcoming transaction (12/02/2025) ![Image](https://github.com/user-attachments/assets/9e7aa511-70ec-4d3d-98d5-e8f4e04173b1) Now there are two entries for 11/25/2025 and the upcoming transaction is still there, even though we posted it for (12/02/2025). ![Image](https://github.com/user-attachments/assets/8e44dcde-bd49-4d58-8b89-aed33b4a5134) ### Where are you hosting Actual? None ### What browsers are you seeing the problem on? _No response_ ### Operating System None
GiteaMirror added the schedulesbuguser interface labels 2026-04-18 05:12:20 -05:00
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 schedules user interface
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#28445
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?