github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-07-16 07:04:23 -05:00
Code Issues 3.0k Packages Projects Releases 58 Wiki Activity

[GH-ISSUE #6270] [Bug]: Can't skip scheduled repeating transaction if set to move before weekend #72406

New Issue
Closed
opened 2026-05-16 12:27:37 -05:00 by GiteaMirror · 9 comments
GiteaMirror commented 2026-05-16 12:27:37 -05:00
Owner
Copy Link

Originally created by @Backspaze on GitHub (Nov 29, 2025).
Original GitHub issue: https://github.com/actualbudget/actual/issues/6270

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

If you create a scheduled repeating transaction, and set it to to repeat on the last day of the month, and set it to move schedule before weekend, you can't skip the next occurrence of the scheduled transaction.

I noticed this today when reconciling, and saw that I'd made the payment on 11/12, while the scheduled transaction for 11/28 had been posted yesterday. I deleted that transaction, which made the scheduled transaction reappear, and I was unable to skip it.

So, without using workarounds, you can't skip a transaction of this kind if you've posted/paid it outside the +- two day window, or if the transaction was skipped in real life for some reason.

How can we reproduce the issue?

Create schedule and try to skip the next occurrence

  • Create a new schedule with a name, payee, account, and amount.
  • In the date picker:
    • From: 11/28/2025 (indefinitely)
    • Repeat every: 1 Months
  • Tick the box for Move schedule, and set it to before weekend.
  • Click Apply.
  • Click Add.
  • Go to the account.
  • Right click the transaction and choose Skip next scheduled date.
  • Nothing happens.

Post transaction early and try to skip the next occurrence

  • Right click the scheduled transaction and choose Post transaction.
  • Change the date to 11/25/2025.
  • The scheduled transaction reappears, and right click > Skip next scheduled date does not do anything.

Where are you hosting Actual?

Pikapods

What browsers are you seeing the problem on?

Firefox

Operating System

Windows 10

Originally created by @Backspaze on GitHub (Nov 29, 2025). Original GitHub issue: https://github.com/actualbudget/actual/issues/6270 ### Verified issue does not already exist? - [x] I have searched and found no existing issue ### What happened? If you create a scheduled repeating transaction, and set it to to repeat on the last day of the month, and set it to move schedule before weekend, you can't skip the next occurrence of the scheduled transaction. I noticed this today when reconciling, and saw that I'd made the payment on 11/12, while the scheduled transaction for 11/28 had been posted yesterday. I deleted that transaction, which made the scheduled transaction reappear, and I was unable to skip it. So, without using workarounds, you can't skip a transaction of this kind if you've posted/paid it outside [the +- two day window](https://actualbudget.org/docs/schedules#how-actual-finds-schedules), or if the transaction was skipped in real life for some reason. ### How can we reproduce the issue? ### Create schedule and try to skip the next occurrence - Create a new schedule with a name, payee, account, and amount. - In the date picker: - **From**: 11/28/2025 (indefinitely) - **Repeat every**: 1 Months - Tick the box for **Move schedule**, and set it to **before** weekend. - Click **Apply**. - Click **Add**. - Go to the account. - Right click the transaction and choose **Skip next scheduled date**. - Nothing happens. ### Post transaction early and try to skip the next occurrence - Right click the scheduled transaction and choose **Post transaction**. - Change the date to 11/25/2025. - The scheduled transaction reappears, and right click > **Skip next scheduled date** does not do anything. ### Where are you hosting Actual? Pikapods ### What browsers are you seeing the problem on? Firefox ### Operating System Windows 10
GiteaMirror added the schedulesbug labels 2026-05-16 12:27:37 -05:00
GiteaMirror commented 2026-05-16 12:27:41 -05:00
Author
Owner
Copy Link

@SalocinHB commented on GitHub (Jan 30, 2026):

+1 on Safari, both Mac and iOS

<!-- gh-comment-id:3825715961 --> @SalocinHB commented on GitHub (Jan 30, 2026): +1 on Safari, both Mac and iOS
GiteaMirror commented 2026-05-16 12:27:41 -05:00
Author
Owner
Copy Link

@aedelor commented on GitHub (Jan 31, 2026):

Also have this issue. Recurring schedule that pays on last day of month, before weekend. Nothing happens if I press skip next.

<!-- gh-comment-id:3827243127 --> @aedelor commented on GitHub (Jan 31, 2026): Also have this issue. Recurring schedule that pays on last day of month, before weekend. Nothing happens if I press skip next.
GiteaMirror commented 2026-05-16 12:27:42 -05:00
Author
Owner
Copy Link

@Backspaze commented on GitHub (Jan 31, 2026):

@SalocinHB @aedelor I believe that the developers prioritize bugs the same way as features - by using the amount of thumbs up (👍) on the first post. While commenting might get some attention, adding a thumbs up will probably bring this higher up in the list faster.

<!-- gh-comment-id:3828876776 --> @Backspaze commented on GitHub (Jan 31, 2026): @SalocinHB @aedelor I believe that the developers prioritize bugs the same way as features - by using the amount of thumbs up (👍) on the first post. While commenting might get some attention, adding a thumbs up will probably bring this higher up in the list faster.
GiteaMirror commented 2026-05-16 12:27:43 -05:00
Author
Owner
Copy Link

@aedelor commented on GitHub (Feb 4, 2026):

Thanks for the advice, I did so!

I also think it's any schedule that is "move before weekend," not just ones that fall at end of month.

<!-- gh-comment-id:3845194318 --> @aedelor commented on GitHub (Feb 4, 2026): Thanks for the advice, I did so! I also think it's any schedule that is "move before weekend," not just ones that fall at end of month.
GiteaMirror commented 2026-05-16 12:27:43 -05:00
Author
Owner
Copy Link

@Backspaze commented on GitHub (Feb 4, 2026):

Great @aedelor, and you're right, it does happen even if you skip the step about last day of the month. I've updated the title and steps to reproduce.

<!-- gh-comment-id:3849445316 --> @Backspaze commented on GitHub (Feb 4, 2026): Great @aedelor, and you're right, it does happen even if you skip the step about last day of the month. I've updated the title and steps to reproduce.
GiteaMirror commented 2026-05-16 12:27:44 -05:00
Author
Owner
Copy Link

@jce-zz commented on GitHub (Feb 16, 2026):

I have the same issue and couldn't figure out why it affected some but not others. THanks to your initial report it's now clear to me as well. Please fix this asap. Thanks!

<!-- gh-comment-id:3908984776 --> @jce-zz commented on GitHub (Feb 16, 2026): I have the same issue and couldn't figure out why it affected some but not others. THanks to your initial report it's now clear to me as well. Please fix this asap. Thanks!
GiteaMirror commented 2026-05-16 12:27:45 -05:00
Author
Owner
Copy Link

@Triscal commented on GitHub (Feb 24, 2026):

Hey all!

So I've put up a fix this for this. If others wanted to test it, that would be great. I believe it just fixes the issue with out impacting other schedules behaviour.

To test you can use the deploy preview link in this comment: https://github.com/actualbudget/actual/pull/7057#issuecomment-3942549607

<!-- gh-comment-id:3949167007 --> @Triscal commented on GitHub (Feb 24, 2026): Hey all! So I've put up a fix this for this. If others wanted to test it, that would be great. I believe it just fixes the issue with out impacting other schedules behaviour. To test you can use the deploy preview link in this comment: https://github.com/actualbudget/actual/pull/7057#issuecomment-3942549607
GiteaMirror commented 2026-05-16 12:27:45 -05:00
Author
Owner
Copy Link

@Backspaze commented on GitHub (Feb 24, 2026):

Thanks @Triscal! I've tested the fix in the deploy preview now, and it seems to work as expected.

<!-- gh-comment-id:3954159991 --> @Backspaze commented on GitHub (Feb 24, 2026): Thanks @Triscal! I've tested the fix in the deploy preview now, and it seems to work as expected.
GiteaMirror commented 2026-05-16 12:27:46 -05:00
Author
Owner
Copy Link

@Triscal commented on GitHub (Feb 24, 2026):

Thanks @Backspaze appreciate the help! It looks like it has been approved and the fix will be merged in March and then appear in April.

<!-- gh-comment-id:3954298438 --> @Triscal commented on GitHub (Feb 24, 2026): Thanks @Backspaze appreciate the help! It looks like it has been approved and the fix will be merged in March and then appear in April.
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
tech-support
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label bug 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#72406
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?