-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
February dates #61
Comments
I haven't touched recurrence code recently, are these transactions' first occur date in February? |
Yes, first time it's ever happened since I started using Financisto. Never
had an issue with Scheduled transactions in for the 29th, 30th and 31st
until this month's instance
…On Sun, Mar 2, 2025, 08:27 tiberiusteng ***@***.***> wrote:
I haven't touched recurrence code recently, are these transactions' first
occur date in February?
—
Reply to this email directly, view it on GitHub
<#61 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGIDCTSN4P34WPBWFOMDJPD2SMINJAVCNFSM6AAAAABYFI4CSOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJSG42TONJSGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
[image: tiberiusteng]*tiberiusteng* left a comment
(tiberiusteng/financisto1-holo#61)
<#61 (comment)>
I haven't touched recurrence code recently, are these transactions' first
occur date in February?
—
Reply to this email directly, view it on GitHub
<#61 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BGIDCTSN4P34WPBWFOMDJPD2SMINJAVCNFSM6AAAAABYFI4CSOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMOJSG42TONJSGU>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
The recurrence date evaluation engine is not change at all. I just checked again to make sure, if you make recurrence that happens at day 29, 30, 31 of the month, they won't be created for months without that day (i.e. 29 30 31 for February, 31 for other months having only 30 days). You probably will want to make it happen at day 28, day 1 or manually copy that transaction from last month when you received notification/statement. I'll make the "evaluate dates" show 15 dates in next version so it'll be easier to catch this situation. |
For now if you want scheduled transaction execute on last day of month (1/31, 2/28, 3/31, 4/30 etc.), you can set I'll try to add a |
You can also try |
This must be a bug introduced since last year in some way.
Scheduled transactions slated for the 29th, 30th and 31st of other months have never given me problems. To my surprise, the app now jumped those transactions altogether
The text was updated successfully, but these errors were encountered: