[GH-ISSUE #1010] [Bug]: Scheduled transactions being posted immediately instead of showing up as pending/missed #7332

New Issue

GiteaMirror · 2026-04-10T17:06:36-05:00

GiteaMirror commented

2026-04-10 17:06:36 -05:00

Originally created by @joaociocca on GitHub (May 7, 2023).
Original GitHub issue: https://github.com/actualbudget/actual/issues/1010

Verified issue does not already exist?

I have searched and found no existing issue

What happened?

Scheduled transactions show up as upcoming when their date is drawing near, as expected... but when that day arrives, instead of showing up as Pending, or Missed, or whatever is the case, they now get added as if they had been posted.

I didn't post this transaction, but it already counts as if it had been. If I manually delete it, it then becomes "missing", as would be expected.

But I noticed this happening for a while now - I missed two scheduled transactions around 20th last month, and every time I open the budget I had to find them again and delete them because they were being posted... for a while, they would revert to missing. Last time, already after the month had changed, they didn't revert, they just vanished. It would be nice if they would stay as missing, as expected.

What error did you receive?

No errors

Where are you hosting Actual?

Docker

What browsers are you seeing the problem on?

Chrome, Other

Operating System

Linux

Originally created by @joaociocca on GitHub (May 7, 2023). Original GitHub issue: https://github.com/actualbudget/actual/issues/1010 ### Verified issue does not already exist? - [X] I have searched and found no existing issue ### What happened? Scheduled transactions show up as upcoming when their date is drawing near, as expected... but when that day arrives, instead of showing up as Pending, or Missed, or whatever is the case, they now get added as if they had been posted. ![image](https://user-images.githubusercontent.com/6473725/236686713-a7137ac4-641c-41a2-96a4-8d5e715889b2.png) I didn't post this transaction, but it already counts as if it had been. If I manually delete it, it then becomes "missing", as would be expected. ![image](https://user-images.githubusercontent.com/6473725/236686823-ebdcca7d-5222-431b-91b4-46fd023ec78d.png) But I noticed this happening for a while now - I missed two scheduled transactions around 20th last month, and every time I open the budget I had to find them again and delete them because they were being posted... for a while, they would revert to missing. Last time, already after the month had changed, they didn't revert, they just vanished. It would be nice if they would stay as missing, as expected. ### What error did you receive? No errors ### Where are you hosting Actual? Docker ### What browsers are you seeing the problem on? Chrome, Other ### Operating System Linux

GiteaMirror added the bug label 2026-04-10 17:06:36 -05:00

GiteaMirror closed this issue

2026-04-10 17:06:37 -05:00

GiteaMirror commented

2026-04-10 17:06:38 -05:00

@j-f1 commented on GitHub (May 7, 2023):

Do you have the “Automatically add transaction” checkbox checked for that schedule? That will auto-create the schedule.

@j-f1 commented on GitHub (May 7, 2023): Do you have the “Automatically add transaction” checkbox checked for that schedule? That will auto-create the schedule.

GiteaMirror commented

2026-04-10 17:06:39 -05:00

@joaociocca commented on GitHub (May 7, 2023):

I agree and understand that it should auto-create the schedule, but at least before (I can't remember if the latest docker update or the previous one) it wouldn't automatically post these transactions, they'd show up as upcoming and when reaching their date or passing them, they'd change from upcoming to missed, until we posted them, as I've been taught in another issue here...

https://github.com/actualbudget/actual/issues/897#issuecomment-1508751809

@joaociocca commented on GitHub (May 7, 2023): I agree and understand that it should auto-create the schedule, but at least before (I can't remember if the latest docker update or the previous one) it wouldn't automatically post these transactions, they'd show up as upcoming and when reaching their date or passing them, they'd change from upcoming to missed, until we posted them, as I've been taught in another issue here... https://github.com/actualbudget/actual/issues/897#issuecomment-1508751809

GiteaMirror commented

2026-04-10 17:06:39 -05:00

@Kidglove57 commented on GitHub (May 7, 2023):

I don't have any technical skille to input. However, as a regular user, I do have one weekly schedule that is NOT marked to auto-post. This schedule came around on Friday last. I can confirm that (for me at least) it behaved correctly and did not auto post.

I am using 2023-05.

@Kidglove57 commented on GitHub (May 7, 2023): I don't have any technical skille to input. However, as a regular user, I do have one weekly schedule that is NOT marked to auto-post. This schedule came around on Friday last. I can confirm that (for me at least) it behaved correctly and did not auto post. I am using 2023-05.

GiteaMirror commented

2026-04-10 17:06:40 -05:00

@joaociocca commented on GitHub (May 8, 2023):

Client version: v23.5.0
Server version: v23.5.0

@joaociocca commented on GitHub (May 8, 2023): Client version: v23.5.0 Server version: v23.5.0

GiteaMirror commented

2026-04-10 17:06:42 -05:00

@Kidglove57 commented on GitHub (May 8, 2023):

Yes sorry - I should have written:
V23.5.0. Hosted on Fly

@Kidglove57 commented on GitHub (May 8, 2023): Yes sorry - I should have written: V23.5.0. Hosted on Fly

GiteaMirror commented

2026-04-10 17:06:42 -05:00

@joaociocca commented on GitHub (May 8, 2023):

that same transaction I had deleted and had returned to missed status, today is back as posted.

@joaociocca commented on GitHub (May 8, 2023): that same transaction I had deleted and had returned to missed status, today is back as posted. ![image](https://user-images.githubusercontent.com/6473725/236831826-09176259-cfc8-49b2-8756-0d3c668856c5.png)

GiteaMirror commented

2026-04-10 17:06:43 -05:00

@j-f1 commented on GitHub (May 8, 2023):

If you have the checkbox to auto create transactions checked for the schedule I think that is the expected behavior.

@j-f1 commented on GitHub (May 8, 2023): If you have the checkbox to auto create transactions checked for the schedule I think that is the expected behavior.

GiteaMirror commented

2026-04-10 17:06:44 -05:00

@joaociocca commented on GitHub (May 8, 2023):

should it be called "auto post transactions" then?

@joaociocca commented on GitHub (May 8, 2023): should it be called "auto post transactions" then?

GiteaMirror commented

2026-04-10 17:06:45 -05:00

@Kidglove57 commented on GitHub (May 8, 2023):

I thought I would just check the exact "check box" wording that is used when setting up a schedule to be auto posted at each due date.

It is "Automatically add transaction". It seems clear enough for my use but very happy if an alternative wording is clearer to others.

The explanatory note then reads "If checked, the schedule will automatically create transactions for you in the specified account"

@Kidglove57 commented on GitHub (May 8, 2023): I thought I would just check the exact "check box" wording that is used when setting up a schedule to be auto posted at each due date. It is "Automatically add transaction". It seems clear enough for my use but very happy if an alternative wording is clearer to others. The explanatory note then reads "If checked, the schedule will automatically create transactions for you in the specified account"

GiteaMirror commented

2026-04-10 17:06:45 -05:00

@joaociocca commented on GitHub (May 8, 2023):

I understand them being two different actions - adding a transaction to the account is one thing, like when it shows as upcoming. Posting being a different one, when you change from upcoming/missed to an actual transaction... but it could be a bug in previous versions that made it behave as I understood, and it wasn't the expected behavior..?

@joaociocca commented on GitHub (May 8, 2023): I understand them being two different actions - adding a transaction to the account is one thing, like when it shows as upcoming. Posting being a different one, when you change from upcoming/missed to an actual transaction... but it could be a bug in previous versions that made it behave as I understood, and it wasn't the expected behavior..?

GiteaMirror commented

2026-04-10 17:06:46 -05:00

@Kidglove57 commented on GitHub (May 8, 2023):

Thanks for explaining further. I had not thought of it that way. I cannot recall a change in behavior since this was first added to the hosted app a year or two back.

I just created a new scheduled payment, due today, but with the box unticked. The transaction immediately showed as "due" and "greyed out" in my account register but not as "posted". I now have the option to select it and choose"skip scheduled date" or tomorrow it will show as "missed"

@Kidglove57 commented on GitHub (May 8, 2023): Thanks for explaining further. I had not thought of it that way. I cannot recall a change in behavior since this was first added to the hosted app a year or two back. I just created a new scheduled payment, due today, but with the box unticked. The transaction immediately showed as "due" and "greyed out" in my account register but not as "posted". I now have the option to select it and choose"skip scheduled date" or tomorrow it will show as "missed"

GiteaMirror commented

2026-04-10 17:06:47 -05:00

@joaociocca commented on GitHub (May 10, 2023):

yeah, now that I unchecked automatically add transaction, they show up as expected...

Still think this description sounds misleading. But maybe it's just me.

@joaociocca commented on GitHub (May 10, 2023): yeah, now that I unchecked automatically add transaction, they show up as expected... ![image](https://github.com/actualbudget/actual/assets/6473725/8f8e93f1-43fb-44d0-8928-bc20b7d94f8b) Still think this description sounds misleading. But maybe it's just me.

GiteaMirror commented

2026-04-10 17:06:48 -05:00

@j-f1 commented on GitHub (May 10, 2023):

If you have a better (concise) description we would be happy to change it!

@j-f1 commented on GitHub (May 10, 2023): If you have a better (concise) description we would be happy to change it!

GiteaMirror commented

2026-04-10 17:06:49 -05:00

@joaociocca commented on GitHub (May 10, 2023):

oh great, browser crashed and I lost the post. Let's start again.

Current text goes like this:

"Automatically add transaction" and "If checked, the schedule will automatically create transactions for you in the specified account".

To me, this sounds like: the transaction won't be shown in the account screen if this box is unchecked. Something like... it'll be here, in the scheduled screen, to help you keep track of it. But it won't show up over there, in your selected account.

When we go to the account screen, and select an upcoming/due/missed scheduled transaction, the actions shown are:

The action that transforms an scheduled transaction into an actual (no pun intended 😅) transaction is "Post transaction". Not "add transaction". And it wouldn't make sense to call it "add transaction", since that's already how it's called including a new one.

If you have a better (concise) description we would be happy to change it!

To answer this directly, I propose changing to: "Automatically post transaction" and "If checked, the schedule will automatically post transactions for you. All scheduled transactions are automatically added in the specified account"

I agree it's not that concise, but it doesn't seem to have a big impact, but explains better the feature:

@joaociocca commented on GitHub (May 10, 2023): oh great, browser crashed and I lost the post. Let's start again. Current text goes like this: ![image](https://github.com/actualbudget/actual/assets/6473725/12ce3098-2c3f-477f-a9f5-cc9960402b14) "Automatically add transaction" and "If checked, the schedule will automatically create transactions for you in the specified account". To me, this sounds like: the transaction won't be shown in the account screen if this box is unchecked. Something like... it'll be here, in the scheduled screen, to help you keep track of it. But it won't show up over there, in your selected account. When we go to the account screen, and select an upcoming/due/missed scheduled transaction, the actions shown are: ![image](https://github.com/actualbudget/actual/assets/6473725/a9ab8b71-ecf9-4d9a-b325-7e0ebb65b4c5) The action that transforms an scheduled transaction into an actual (no pun intended 😅) transaction is "Post transaction". Not "add transaction". And it wouldn't make sense to call it "add transaction", since that's already how it's called including a new one. > If you have a better (concise) description we would be happy to change it! To answer this directly, I propose changing to: "Automatically post transaction" and "If checked, the schedule will automatically post transactions for you. All scheduled transactions are automatically added in the specified account" I agree it's not that concise, but it doesn't seem to have a big impact, but explains better the feature: ![image](https://github.com/actualbudget/actual/assets/6473725/b99faf8c-65c5-4b38-aece-37ccf27433fc)

GiteaMirror commented

2026-04-10 17:06:50 -05:00

@joaociocca commented on GitHub (May 10, 2023):

Just found out I have another beef with the feature. When posting a missed scheduled transaction, it'll post with the original date. But that may kind of get lost in the sea of transactions? Would be nice to have two different actions for it: post on original date, and post today.

@joaociocca commented on GitHub (May 10, 2023): Just found out I have another beef with the feature. When posting a missed scheduled transaction, it'll post with the original date. But that may kind of get lost in the sea of transactions? Would be nice to have two different actions for it: post on original date, and post today.

GiteaMirror commented

2026-04-10 17:06:50 -05:00

@rich-howell commented on GitHub (May 10, 2023):

Just found out I have another beef with the feature. When posting a missed scheduled transaction, it'll post with the original date. But that may kind of get lost in the sea of transactions? Would be nice to have two different actions for it: post on original date, and post today.

This should go as a separate issue

@rich-howell commented on GitHub (May 10, 2023): > Just found out I have another beef with the feature. When posting a missed scheduled transaction, it'll post with the original date. But that may kind of get lost in the sea of transactions? Would be nice to have two different actions for it: post on original date, and post today. This should go as a separate issue

GiteaMirror commented

2026-04-10 17:06:50 -05:00

@joaociocca commented on GitHub (May 10, 2023):

Just found out I have another beef with the feature. When posting a missed scheduled transaction, it'll post with the original date. But that may kind of get lost in the sea of transactions? Would be nice to have two different actions for it: post on original date, and post today.

This should go as a separate issue

#1020

@joaociocca commented on GitHub (May 10, 2023): > > Just found out I have another beef with the feature. When posting a missed scheduled transaction, it'll post with the original date. But that may kind of get lost in the sea of transactions? Would be nice to have two different actions for it: post on original date, and post today. > > This should go as a separate issue #1020

GiteaMirror commented

2026-04-10 17:06:51 -05:00

@joaociocca commented on GitHub (May 11, 2023):

oh gods, there's more stuff wrong to scheduling and posting. So, I have this transaction that has max due date on the 16th. But I paid for it today. So I posted the upcoming scheduled transaction.

Actual decided that, no matter if it identifies as being part of the schedule (there's the schedule arrows beside it), and despite having been posted from the upcoming transaction, it cloned the upcoming into a new transaction but kept the upcoming transaction there...

And on the schedule, it doesn't recognize this as being paid.

even the detailed modal is correct and recognizes the transaction as being part of the schedule...

@joaociocca commented on GitHub (May 11, 2023): oh gods, there's more stuff wrong to scheduling and posting. So, I have this transaction that has max due date on the 16th. But I paid for it today. So I posted the upcoming scheduled transaction. Actual decided that, no matter if it identifies as being part of the schedule (there's the schedule arrows beside it), and despite having been posted from the upcoming transaction, it cloned the upcoming into a new transaction but kept the upcoming transaction there... ![image](https://github.com/actualbudget/actual/assets/6473725/61c7c75a-dfc2-4b94-bd9c-35d1cdea7cbf) And on the schedule, it doesn't recognize this as being paid. ![image](https://github.com/actualbudget/actual/assets/6473725/21c60d42-85b5-450a-8c96-4a2dfe6cab1b) even the detailed modal is correct and recognizes the transaction as being part of the schedule... ![image](https://github.com/actualbudget/actual/assets/6473725/976cbe67-5973-42a3-a886-3ee9ffad473b)

GiteaMirror commented

2026-04-10 17:06:52 -05:00

@shall0pass commented on GitHub (May 11, 2023):

I always looked at the italicized transactions from schedules as future possible entries (but not transactions yet). It's just a preview. If they're automatically entered or manually posted they count towards the account balances and become real entries.

What you're seeing in your last post is the 4 2 day window (https://actualbudget.github.io/docs/Budgeting/schedules#how-actual-finds-schedules) actual looks at to match transactions to a schedule. Since you posted a transaction and then changed the date to 6 days early, you're no longer in the window and it won't match to the schedule. I know it's by design, but I'm not sure what the reasoning was.

I wouldn't say anything is necessarily broken. It's just not probably what you're used to.

@shall0pass commented on GitHub (May 11, 2023): I always looked at the italicized transactions from schedules as future possible entries (but not transactions yet). It's just a preview. If they're automatically entered or manually posted they count towards the account balances and become real entries. What you're seeing in your last post is the ~4~ 2 day window (https://actualbudget.github.io/docs/Budgeting/schedules#how-actual-finds-schedules) actual looks at to match transactions to a schedule. Since you posted a transaction and then changed the date to 6 days early, you're no longer in the window and it won't match to the schedule. I know it's by design, but I'm not sure what the reasoning was. I wouldn't say anything is necessarily broken. It's just not probably what you're used to.

GiteaMirror commented

2026-04-10 17:06:52 -05:00

@MatissJanis commented on GitHub (Aug 26, 2023):

I have to agree with @shall0pass that this works as-expected.

Closing this off since the original issue is no-op.

@MatissJanis commented on GitHub (Aug 26, 2023): I have to agree with @shall0pass that this works as-expected. Closing this off since the original issue is no-op.

GiteaMirror referenced this issue

2026-04-10 20:19:57 -05:00

[GH-ISSUE #7332] [Bug]: The custom report editor is retaining unsaved settings between viewing custom reports #9990

GiteaMirror referenced this issue

2026-04-10 22:14:49 -05:00

[PR #7356] [MERGED] Fix custom report editor retaining unsaved settings #14160

GiteaMirror referenced this issue

2026-04-14 20:11:00 -05:00

[GH-ISSUE #7332] [Bug]: The custom report editor is retaining unsaved settings between viewing custom reports #17289

GiteaMirror referenced this issue

2026-04-14 22:05:38 -05:00

[PR #7356] [MERGED] Fix custom report editor retaining unsaved settings #21468

GiteaMirror referenced this issue

2026-04-16 18:48:25 -05:00

[PR #7356] [MERGED] Fix custom report editor retaining unsaved settings #25715

GiteaMirror referenced this issue

2026-04-18 05:35:22 -05:00

[GH-ISSUE #7332] [Bug]: The custom report editor is retaining unsaved settings between viewing custom reports #28843

GiteaMirror referenced this issue

2026-04-18 08:57:55 -05:00

[PR #7356] [MERGED] Fix custom report editor retaining unsaved settings #33030

GiteaMirror referenced this issue

2026-04-21 00:14:12 -05:00

[PR #7356] [MERGED] Fix custom report editor retaining unsaved settings #37300

GiteaMirror referenced this issue

2026-04-23 14:19:30 -05:00

[PR #7356] [MERGED] Fix custom report editor retaining unsaved settings #41536

GiteaMirror referenced this issue

2026-04-26 06:34:15 -05:00

[GH-ISSUE #7332] [Bug]: The custom report editor is retaining unsaved settings between viewing custom reports #44710

GiteaMirror referenced this issue

2026-04-26 10:47:52 -05:00

[PR #7356] [MERGED] Fix custom report editor retaining unsaved settings #48925

GiteaMirror referenced this issue

2026-04-30 20:22:56 -05:00

[GH-ISSUE #7332] [Bug]: The custom report editor is retaining unsaved settings between viewing custom reports #52174

GiteaMirror referenced this issue

2026-05-01 04:16:07 -05:00

[PR #7356] [MERGED] Fix custom report editor retaining unsaved settings #56409

Sign in to join this conversation.

Branches Tags

master

claude/hide-default-categories-1cwBZ

matiss/crdt-source-loading

youngcw/unlock-duplicates

matiss/crdt-protobuf

release/26.5.0

claude/update-issue-template-ykMNn

claude/fix-issue-7667-DPXi3

cursor/formula-feedback-improvements-4223

cursor/resolve-pr-7449-ee11

claude/fix-typescript-build-error-JPtZ5

jfdoming/api-tokens-part-3

jfdoming/api-tokens-part-2

jfdoming/api-tokens-part-1

claude/speed-up-vrt-workflow-ZAyI5

claude/crdt-version-auto-publish-Ph1BH

copilot/add-repository-configs-to-packages

worktree-compressed-drifting-ritchie

worktree-mellow-strolling-dawn

matiss/browser-api

claude/api-consumer-verification-kfz1K

feature/enable-banking

cursor/transaction-table-rewrite-f077

pr-7454

claude/fix-issue-7410-LLLQ4

release/v100.0.0

revert-7350-trim-deps

revert-7220-sankey-report

revert-7242-fix/split-parent-update-corruption

revert-7281-generate-icons

claude/electron-to-tauri-migration-LjBN8

worktree-remotion

release/vv26.4.0-pre

claude/browser-compatible-api-QbhHh

claude/improve-cli-transactions-waTUY

claude/publish-react-native-ios-j8qoT

js-proxy

claude/fix-flaky-ci-job-5gDdz

react-query-rules

react-query-useSchedules

claude/nightly-theme-validation-scan-DzOGD

claude/debug-simplefin-error-ZuKzB

matiss/desktop-client-subpath-imports

claude/fix-simplefin-ssrf-T31gX

claude/release-notes-validation-X7rvR

add-claude-github-actions-1772738270730

cursor/sync-performance-notification-9899

react-query-prefs

matiss/chunked-sync-and-progress-ux

v26.2.1

copilot/sub-pr-6880

fix-react-query-clear-on-close-budget

copilot/sub-pr-6140

feat/auto-note

feat/scoped-bank-sync

cursor/desktop-transactions-react-table-1d0c

fix-exhaustive-deps-App

copilot/fix-find-replace-bug

release/v26.2.0-pre

matiss/browser-tests

mobile-fix-drag-and-drop-across-groups

budget-table-v2

PayeeAutocomplete2

pglite

bugfix/plugins/fix-plugins-sw

feat/plugins/plugins-core-package

prerelease

matiss/unicode-minus-fix

cursor/fix-actual-github-issue-6206-gemini-3-pro-preview-9c37

TransactionFormPage

cursor/implement-mortgage-and-loan-account-type-78ca

tests-update-fill-with-pressSequentially

mobile/link-modal

deps/25.11

cursor/fix-update-vrt-apply-ci-job-dispatch-b324

sync-server-plugins

cursor/propose-patch-for-github-issue-5680-2a18

fix/compiler-preserve-inner-dollar-escapes

cursor/analyze-actual-budget-issue-and-propose-fix-5b70

coderabbitai/docstrings/0c070e5

cursor/add-wip-prefix-and-comment-to-prs-d78d

jfdoming/08-21-auto-focus-on-navigate-in-all-browsers

show-totals-on-mobile-budget-banners

allow-child-transactions-make-transfer

mobile-calculator-keyboard

payee-geolocation

enhance/restore_scroll_position

dm-fix-second-click-on-mobile-new-transaction-2

scrollToLocationBudget

alert-autofix-38

tsconfig-composite

mobile-fix-uncategorized-transactions-on-tracking-budgets

server-budget-handlers

fix-sql-injection-in-cleanup-template

non-chrome-draggable-workaround

mobile-budget-page-swipe-navigation

ts-db-all

stable

dark-theme-with-brand-colors

fix-mobile-delete-group

ts-db-select

UnderKoen/reconcile-context-menu

master-before-server-merge

v25.2.1

ts-runQuery

rename-redux-hooks

UnderKoen/3557-persist-state-in-history

remove-redux-CLOSE_BUDGET

fix-exhaustive-deps-errors-FinancesApp

redux-toolkit-createSlice-backup

accounts-function-component

ts-useSplitsExpanded

loot-core-server-package

useTransactios-in-TransactionEdit

react-aria-input

move-redux-to-desktop-client

QueryState-type

fix-themes-applied-late

mobile-vrts

revert-3295-spendingCardFix

react-aria-button-4

split-payee-on-mobile

twk3/pin-apis-crdt

notes-tag-autocomplete

ts-LoadBackup

dnd-kit

package-upgrades

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/actual#7332