Allow to set how many future instances of a recurring transaction to create in advance #50

New Issue

adam · 2025-12-28T23:24:42+01:00

adam commented

2025-12-28 23:24:42 +01:00

Originally created by @eitchtee on GitHub (Aug 6, 2025).

Originally assigned to: @eitchtee on GitHub.

Discussed in https://github.com/eitchtee/WYGIWYH/discussions/306

^{Originally posted by torchedplatypi August 5, 2025}
I have just set up your app, and I'm thrilled with how it works. The workflow and approach mirror what I have done in a notepad for a long time. Double entry and even envelope accounting are overkill for me, as I just want to track monthly differential (hopefully surplus) and see net worth macro trend over time.

To that end, since I've just set it up, I only have projected net worth, and I found an unfortunate side effect of this bit that is described in the wiki under Recurring Transaction -> Other Information:

>WYGIWYH tries to keep at most 6 future transactions created at any time.

I imagine this is for performance reasons, since End Date is optional, so there must be a cutoff at some point. Is this or could this be configurable anywhere? Or time-based instead of count-based?

Because my biweekly paycheck is at a tighter frequency than my monthly house payment and my bi-annual car insurance payment (for examples), it throws off the net worth projection graph more than 3 months (6 biweekly checks) in the future.

i.e. 6 monthly house payments equates to 12 biweekly paychecks, so the 4th projected house payment begins dropping the net worth projection even though paychecks 7 and 8 would be cashing in that time and covering that drop plus some surplus.

For illustration:

Originally created by @eitchtee on GitHub (Aug 6, 2025). Originally assigned to: @eitchtee on GitHub. ### Discussed in https://github.com/eitchtee/WYGIWYH/discussions/306 <div type='discussions-op-text'> <sup>Originally posted by **torchedplatypi** August 5, 2025</sup> I have just set up your app, and I'm thrilled with how it works. The workflow and approach mirror what I have done in a notepad for a long time. Double entry and even envelope accounting are overkill for me, as I just want to track monthly differential (hopefully surplus) and see net worth macro trend over time. To that end, since I've just set it up, I _only_ have projected net worth, and I found an unfortunate side effect of this bit that is described in the wiki under Recurring Transaction -> Other Information: **>WYGIWYH tries to keep at most 6 future transactions created at any time.** I imagine this is for performance reasons, since End Date is optional, so there must be a cutoff at some point. **Is this or could this be configurable anywhere? Or time-based instead of count-based?** Because my biweekly paycheck is at a tighter frequency than my monthly house payment and my bi-annual car insurance payment (for examples), it throws off the net worth projection graph more than 3 months (6 biweekly checks) in the future. i.e. 6 monthly house payments equates to 12 biweekly paychecks, so the 4th projected house payment begins dropping the net worth projection even though paychecks 7 and 8 _would_ be cashing in that time and covering that drop plus some surplus. For illustration: <img width="580" height="378" alt="image" src="https://github.com/user-attachments/assets/09c5b5a2-b017-405e-921b-14b6052781ce" /> </div>

adam added the enhancement label 2025-12-28 23:24:42 +01:00

adam closed this issue

2025-12-28 23:24:42 +01:00

adam commented

2025-12-28 23:24:43 +01:00

@eitchtee commented on GitHub (Aug 6, 2025):

@torchedplatypi this has been implemented and will be available on the next update (aiming at releasing this weekend).

I've added a new field to the recurring transaction form, this defaults to 6 but can be changed to any number higher or equal to 1.

For existing recurring transactions, the default will also be 6, so you'll need to edit those with your desired number. Keep in mind that edits aren't reflected immediately, instead they will take effect on the next run of the background task responsible for creating recurring transactions, at midnight (usually UTC, unless you've changed the env variable). If you want to see the changes immediately, run python manage.py procrastinate defer generate_recurring_transactions inside WYGIWYH container.

@eitchtee commented on GitHub (Aug 6, 2025): @torchedplatypi this has been implemented and will be available on the next update (aiming at releasing this weekend). I've added a new field to the recurring transaction form, this defaults to 6 but can be changed to any number higher or equal to 1. <img width="672" height="82" alt="Image" src="https://github.com/user-attachments/assets/27d88778-55ac-466a-969b-d17d389623c1" /> For existing recurring transactions, the default will also be 6, so you'll need to edit those with your desired number. Keep in mind that edits aren't reflected immediately, instead they will take effect on the next run of the background task responsible for creating recurring transactions, at midnight (usually UTC, unless you've changed the env variable). If you want to see the changes immediately, run `python manage.py procrastinate defer generate_recurring_transactions` inside WYGIWYH container.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/WYGIWYH#50