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

[GH-ISSUE #1957] [Bug]: Posting a scheduled transaction early does not remove the schedule #7694

New Issue
Open
opened 2026-04-10 17:39:41 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-04-10 17:39:41 -05:00
Owner
Copy Link

Originally created by @joel-jeremy on GitHub (Nov 22, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1957

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

When I pay a bill ahead of it's due date, I post the scheduled transaction in Actual and change the date to the actual date of payment. When I change the date of the posted transaction, the schedule reappears again in the transactions table.

Steps to reproduce:

  1. Setup an upcoming scheduled transaction
    image
  2. Post the scheduled transaction
    image
  3. Change the transaction date to the date today
    image
  4. The upcoming scheduled transaction reappears

What error did you receive?

No response

Where are you hosting Actual?

Fly.io

What browsers are you seeing the problem on?

Chrome, Other

Operating System

Windows 11

Originally created by @joel-jeremy on GitHub (Nov 22, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/1957 ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? When I pay a bill ahead of it's due date, I post the scheduled transaction in Actual and change the date to the actual date of payment. When I change the date of the posted transaction, the schedule reappears again in the transactions table. Steps to reproduce: 1. Setup an upcoming scheduled transaction ![image](https://github.com/actualbudget/actual/assets/20313680/7cbac03a-9d78-4511-9fc5-a664488b67cc) 2. Post the scheduled transaction ![image](https://github.com/actualbudget/actual/assets/20313680/2f95ed6e-07dd-490b-bc3a-25659e95d71c) 3. Change the transaction date to the date today ![image](https://github.com/actualbudget/actual/assets/20313680/7cee5ebb-9ff3-4b88-927e-c8c2a7b42424) 4. The upcoming scheduled transaction reappears ### What error did you receive? _No response_ ### Where are you hosting Actual? Fly.io ### What browsers are you seeing the problem on? Chrome, Other ### Operating System Windows 11
GiteaMirror added the bughelp wantedschedules labels 2026-04-10 17:39:41 -05:00
GiteaMirror commented 2026-04-10 17:39:43 -05:00
Author
Owner
Copy Link

@Kidglove57 commented on GitHub (Dec 30, 2023):

This happened to me in December:

  1. I was paid a week early due to Christmas.
  2. I tried posting the scheduled transaction early but it immediately recreated itself. I used CmD Z to get out of that one and let the schedule be.
  3. In the end it came up as missed so I tried to skip it. Absolutely nothing happened when I selected and skipped.
  4. So I ended up with two transactions one of which I had to alter to give it a Nil value.
<!-- gh-comment-id:1872585921 --> @Kidglove57 commented on GitHub (Dec 30, 2023): This happened to me in December: 1) I was paid a week early due to Christmas. 2) I tried posting the scheduled transaction early but it immediately recreated itself. I used CmD Z to get out of that one and let the schedule be. 3) In the end it came up as missed so I tried to skip it. Absolutely nothing happened when I selected and skipped. 4) So I ended up with two transactions one of which I had to alter to give it a Nil value.
GiteaMirror commented 2026-04-10 17:39:43 -05:00
Author
Owner
Copy Link

@CrimsonFlash commented on GitHub (Mar 21, 2025):

This is happening to me as well. Exactly as you have shown.

What error did you receive?
No error

Where are you hosting Actual?
Bare metal from source
Server v25.3.1
Client v25.3.1

What browsers are you seeing the problem on?
Firefox, Chrome, macOS native app

Operating System
Server: Windows Server 2025
Client: Windows 10, macOS 15.3.2

<!-- gh-comment-id:2743442568 --> @CrimsonFlash commented on GitHub (Mar 21, 2025): This is happening to me as well. Exactly as you have shown. **What error did you receive?** No error **Where are you hosting Actual?** Bare metal from source Server v25.3.1 Client v25.3.1 **What browsers are you seeing the problem on?** Firefox, Chrome, macOS native app **Operating System** Server: Windows Server 2025 Client: Windows 10, macOS 15.3.2
GiteaMirror commented 2026-04-10 17:39:44 -05:00
Author
Owner
Copy Link

@RegalMonkey commented on GitHub (Mar 9, 2026):

Looks like this is still a factor in the latest docker version, an interesting addition to it, even if you post the scheduled transaction as paid on the regular day and then change the date to the current day, it'll recreate the upcoming schedule item.

<!-- gh-comment-id:4023317786 --> @RegalMonkey commented on GitHub (Mar 9, 2026): Looks like this is still a factor in the latest docker version, an interesting addition to it, even if you post the scheduled transaction as paid on the regular day and then change the date to the current day, it'll recreate the upcoming schedule item.
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 help wanted 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#7694
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?