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

[GH-ISSUE #6872] [Bug]: Upcoming status not updated when multiple scheduled transactions are missed #17132

New Issue
Closed
opened 2026-04-14 20:03:43 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-14 20:03:43 -05:00
Owner
Copy Link

Originally created by @jeremyj on GitHub (Feb 5, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/6872

What happened?

Image

When two scheduled transactions are missed in sequence, only the first one is marked as missed.
The second transaction continues to appear as upcoming, even though its due date has already passed.

The second transaction is only correctly marked as missed after the first missed transaction is manually marked as skipped.

How can we reproduce the issue?

Steps to Reproduce

  1. Create a recurring scheduled transaction.
  2. Let two consecutive occurrences pass without completing them.
  3. Open the scheduled transactions list.
  4. Check their status.

Expected Behavior

Both overdue transactions should be automatically marked as missed.

Actual Behavior

Only the first transaction is marked as missed.
The second remains upcoming until the first is skipped.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome

Operating System

Linux

Originally created by @jeremyj on GitHub (Feb 5, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/6872 ### What happened? <img width="1597" height="85" alt="Image" src="https://github.com/user-attachments/assets/feffdd06-065c-4b73-975c-af20081fc152" /> When two scheduled transactions are missed in sequence, only the first one is marked as **missed**. The second transaction continues to appear as **upcoming**, even though its due date has already passed. The second transaction is only correctly marked as missed after the first missed transaction is manually marked as **skipped**. ### How can we reproduce the issue? ### Steps to Reproduce 1. Create a recurring scheduled transaction. 2. Let two consecutive occurrences pass without completing them. 3. Open the scheduled transactions list. 4. Check their status. --- ### Expected Behavior Both overdue transactions should be automatically marked as **missed**. --- ### Actual Behavior Only the first transaction is marked as **missed**. The second remains **upcoming** until the first is skipped. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Chrome ### Operating System Linux
GiteaMirror added the budgetingschedulesgood first issuebug labels 2026-04-14 20:03:43 -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 budgeting bug good first issue schedules
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#17132
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?