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 #923] [Bug]: Skip scheduled date doesn't affect missed transactions #7298

New Issue
Closed
opened 2026-04-10 17:03:49 -05:00 by GiteaMirror · 6 comments
GiteaMirror commented 2026-04-10 17:03:49 -05:00
Owner
Copy Link

Originally created by @shall0pass on GitHub (Apr 19, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/923

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

I am not able to skip a missed schedule. I tried posting the schedule and then deleting it, but the schedule comes back as missed. I created the animation using the https://actualbudget.netlify.app site.

skip_scheduled_date

What error did you receive?

No response

Where are you hosting Actual?

None

What browsers are you seeing the problem on?

Chrome

Operating System

Windows 10

Originally created by @shall0pass on GitHub (Apr 19, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/923 ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? I am not able to skip a missed schedule. I tried posting the schedule and then deleting it, but the schedule comes back as missed. I created the animation using the https://actualbudget.netlify.app site. ![skip_scheduled_date](https://user-images.githubusercontent.com/20625555/233106837-fa9c4d2c-bd26-401d-a0ee-fb602587aa5f.gif) ### What error did you receive? _No response_ ### Where are you hosting Actual? None ### What browsers are you seeing the problem on? Chrome ### Operating System Windows 10
GiteaMirror added the user interfacebugschedules labels 2026-04-10 17:03:49 -05:00
GiteaMirror commented 2026-04-10 17:03:50 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Apr 28, 2023):

Does this happen with schedules that repeat? With schedules that do not repeat? Or both?

I was able to reproduce with a schedule that does not repeat.

<!-- gh-comment-id:1528163690 --> @MatissJanis commented on GitHub (Apr 28, 2023): Does this happen with schedules that repeat? With schedules that do not repeat? Or both? I was able to reproduce with a schedule that does not repeat.
GiteaMirror commented 2026-04-10 17:03:51 -05:00
Author
Owner
Copy Link

@shall0pass commented on GitHub (Apr 29, 2023):

I thought I included a shot of the schedule screen when I made that. My apologies, as it's clear I didn't. This only occurs on non repeating transactions for me.

<!-- gh-comment-id:1528286777 --> @shall0pass commented on GitHub (Apr 29, 2023): I thought I included a shot of the schedule screen when I made that. My apologies, as it's clear I didn't. This only occurs on non repeating transactions for me.
GiteaMirror commented 2026-04-10 17:03:51 -05:00
Author
Owner
Copy Link

@MatissJanis commented on GitHub (Apr 29, 2023):

I wonder how we should handle "skipping" of non-repeating schedules. Would that just "complete" the schedule? Or perhaps delete it?

I'm more inclined to say it would "complete" it. What do you think?

<!-- gh-comment-id:1528721206 --> @MatissJanis commented on GitHub (Apr 29, 2023): I wonder how we should handle "skipping" of non-repeating schedules. Would that just "complete" the schedule? Or perhaps delete it? I'm more inclined to say it would "complete" it. What do you think?
GiteaMirror commented 2026-04-10 17:03:51 -05:00
Author
Owner
Copy Link

@shall0pass commented on GitHub (Apr 29, 2023):

I think either is reasonable. Is there a reason to keep it in the record if it never happened though?

<!-- gh-comment-id:1528761407 --> @shall0pass commented on GitHub (Apr 29, 2023): I think either is reasonable. Is there a reason to keep it in the record if it never happened though?
GiteaMirror commented 2026-04-10 17:03:52 -05:00
Author
Owner
Copy Link

@j-f1 commented on GitHub (Apr 29, 2023):

Maybe the menu item could change to “delete” if the schedule doesn’t repeat?

<!-- gh-comment-id:1528784790 --> @j-f1 commented on GitHub (Apr 29, 2023): Maybe the menu item could change to “delete” if the schedule doesn’t repeat?
GiteaMirror commented 2026-04-10 17:03:53 -05:00
Author
Owner
Copy Link

@shall0pass commented on GitHub (Apr 29, 2023):

Possibly, but only if a single transaction is selected? If multiple are selected, I'm not sure it would make sense especially if some are recurring and some non-recurring. This seems more complicated that I originally anticipated.

<!-- gh-comment-id:1528792817 --> @shall0pass commented on GitHub (Apr 29, 2023): Possibly, but only if a single transaction is selected? If multiple are selected, I'm not sure it would make sense especially if some are recurring and some non-recurring. This seems more complicated that I originally anticipated.
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#7298
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?