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

[GH-ISSUE #7132] [Bug]: Deleting an automatically added scheduled transaction does not restore the schedule to “Missed” #44647

New Issue
Closed
opened 2026-04-26 06:24:16 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-26 06:24:16 -05:00
Owner
Copy Link

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

What happened?

I deleted an automatically added transaction that was created by a schedule after the scheduled date had already passed.

Expected behavior:
After deleting the generated transaction, the schedule occurrence should return to the “Missed” state, since the due date is already in the past.

Actual behavior:
The schedule does not reappear as “Missed”. The missed occurrence seems to disappear entirely instead of being restored.

How can we reproduce the issue?

  1. Create a scheduled transaction that is automatically added to the ledger.
  2. Let the scheduled date pass so the transaction is created.
  3. Delete the automatically added transaction from the ledger after the scheduled date.
  4. Check the scheduled transactions list.

Expected:
The schedule occurrence should appear as Missed.

Actual:
The missed occurrence does not reappear.

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome

Operating System

Linux

Originally created by @jeremyj on GitHub (Mar 5, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/7132 ### What happened? I deleted an automatically added transaction that was created by a schedule after the scheduled date had already passed. Expected behavior: After deleting the generated transaction, the schedule occurrence should return to the “Missed” state, since the due date is already in the past. Actual behavior: The schedule does not reappear as “Missed”. The missed occurrence seems to disappear entirely instead of being restored. ### How can we reproduce the issue? 1. Create a scheduled transaction that is automatically added to the ledger. 2. Let the scheduled date pass so the transaction is created. 3. Delete the automatically added transaction from the ledger after the scheduled date. 4. Check the scheduled transactions list. Expected: The schedule occurrence should appear as Missed. Actual: The missed occurrence does not reappear. ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Chrome ### Operating System Linux
GiteaMirror added the needs infobug labels 2026-04-26 06:24:16 -05:00
GiteaMirror commented 2026-04-26 06:24:21 -05:00
Author
Owner
Copy Link

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

I don't know if I would consider this a bug. Actual did everything you asked it to. Why should Actual assume that you still wanted the schedule if you deleted it?

<!-- gh-comment-id:4005643255 --> @youngcw commented on GitHub (Mar 5, 2026): I don't know if I would consider this a bug. Actual did everything you asked it to. Why should Actual assume that you still wanted the schedule if you deleted it?
GiteaMirror commented 2026-04-26 06:24:22 -05:00
Author
Owner
Copy Link

@jeremyj commented on GitHub (Mar 5, 2026):

The scheduled transaction is created automatically, and later the same transaction is imported by bank sync and Actual doesn’t match them automatically (maybe because it’s a USD transaction the amount varies slightly due to USD/EUR exchange rates). At that point I can’t merge or link the two transactions successfully (maybe related to this bug? https://github.com/actualbudget/actual/issues/6997), so the only practical option left is to delete the automatically created scheduled transaction and keep the imported one.

<!-- gh-comment-id:4006434657 --> @jeremyj commented on GitHub (Mar 5, 2026): The scheduled transaction is created automatically, and later the same transaction is imported by bank sync and Actual doesn’t match them automatically (maybe because it’s a USD transaction the amount varies slightly due to USD/EUR exchange rates). At that point I can’t merge or link the two transactions successfully (maybe related to this bug? https://github.com/actualbudget/actual/issues/6997), so the only practical option left is to delete the automatically created scheduled transaction and keep the imported one.
GiteaMirror commented 2026-04-26 06:24:23 -05:00
Author
Owner
Copy Link

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

That all sounds fine.
I recommend:

  1. Don't auto post schedules if you use bank sync (especially if the amount varies)
  2. Use an approximate amount in your schedule to catch variation in amounts
  3. If the schedule still doesn't link, then select the transaction and say "link schedule" to manually connect to the schedule so it will be considered paid.
<!-- gh-comment-id:4006486074 --> @youngcw commented on GitHub (Mar 5, 2026): That all sounds fine. I recommend: 1. Don't auto post schedules if you use bank sync (especially if the amount varies) 2. Use an approximate amount in your schedule to catch variation in amounts 3. If the schedule still doesn't link, then select the transaction and say "link schedule" to manually connect to the schedule so it will be considered paid.
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 needs info
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#44647
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?