Semi-Monthly scheduled transaction is constantly deleting 1 of the two instances (Q Mac)

npace

I have a semi-monthly paycheck that's been scheduled for several years and just in the last 60 days or so it is deleting 1 of those monthly instances every time I update my accounts. So my paycheck on the 15th and end of month ends up only showing up on the 15th and not the 30th/31st. I have to reset it every time. I can reset it no problem, and I can even do two separate monthly instances instead, but that seems weird and it's never had this problem before. Very strange.

Jon

You're not the first person to report that issue.

https://community.quicken.com/discussion/7972103/scheduled-deposits-disappearing-q-mac

Quicken Carlos

Hi @npace,

Thank you for reaching out to the Quicken Community and letting us know that you’re experiencing this issue.

I recommend submitting your logs via Help > Report a Problem.

Once you’ve uploaded the report, please let me know so I can add the information to the investigation ticket.

I look forward to your reply!

(CTP-16838)

Quicken Carlos

Hi @npace,

I just wanted to follow up since I haven’t heard back from you. I’m checking in to see if you still need assistance.

UKR

As a Quicken for Windows user, I am able to reproduce the error with the "vanishing 2nd payment, due on the 31st", but only under certain circumstances.

Assume the following conditions:

• Today is the 1st of May (a month with 31 days)
• My account register is set to display future scheduled reminders for the next 30 days

This makes the future reminder transaction for the 31st fall off the end of the next 30 days period (which, on 5/1, is defined as 5/1 - 5/30)

When I look at the same transaction again the next day, the 2nd of May, the next 30 days period has advanced a day, 5/2 - 5/31, and both of this reminder's instances, 5/15 and 5/31, display correctly.

IMHO, this is not a bug. It's working as designed (don't you hate it when someone says that? :-)
But it's puzzling.

Sometimes I wish we had a calendar with 12 months at 30 days each. No leap year. No short or long months.
No fudging needed with interest calculations.
Someone please go out into space with long crowbar and push the earth into a new orbit, with exactly 360 days per year.
😃

jacobs

@UKR That's not the problem being described in this thread. It's not a visibility problem on the first day of a 31-day month; it's a problem where a bi-monthly transaction date is missed entirely. There's more details in the other thread linked above, where a user describes this:

In the Register, with "Next 12 Months" it showed all future deposits except the next one. For example, 5/15 was missing - 5/31, 6/15, 6/30 etc. all showed as expected

There have been follow-up reports, so it may have been a bug which was fixed in a recent update. It would be helpful to hear from @npace whether this problem is still present or has now been fixed.