Thank you for taking the time to visit the Community to report this issue, although I apologize that you're experiencing this trouble.
First, If you haven't already and open Quicken and go to the Help menu > Report a Problem. There have been ongoing issues with syncing. This report will help contribute to the research of these issues.
Do you use the mobile or web app at all? If not, can you confirm if the option to sync to the mobile/ web is on. To confirm, please navigate to Edit > Preferences > Mobile & Web, there will be an on-off toggle. Can you also navigate to the One Step Update settings and confirm if sync to the cloud is selected there?
If either of these options is enabled please disable them and see if this resolves the issue. If this does resolve the issue, it's possible that you may need to move forward without syncing to the cloud or mobile app until the issue has been corrected.
I hope this helps to clarify.
-Quicken Tyka
Apologies in advance for the frustration embedded in this post, but I don't have the time it would take to neutralize it.
I've had this issue ever since probably 15 or 20 years ago. After years of not upgrading to the new Quicken subscription model (why would I upgrade when Quicken won't pay attention to this issue?), I finally figured that maybe if I purchase the new version of Quicken, surely the bug would be gone after all these years. But after 2 decades, evidently the Quicken coders just don't seem to think this issue is important. (So I unsubscribed and just use the software offline today. I will never pay another cent to Quicken until this bug is resolved.)
I took a screenshot of last month's reconciled transactions on the Reconciliation page of Quicken (below). This month as I reconciled, THREE transactions that were already reconciled last month now magically show up unreconciled this month for no reason whatsoever. I DO NOT sync anything (in Preferences > Mobile & Web, Sync is set to OFF). I use only the desktop version without any downloading of anything, and ALL I do is just simply enter transactions from receipts, then use the Reconcile feature (CTRL-R) once a month to reconcile. That's it! My needs for this software couldn't get any more simple/basic than that.
This has happened more times than I can even count. I do not want anyone to tell me, "you must have accidentally clicked on those transactions and toggled their reconciliation status." No. No way did that happen three times, let alone all the countless times in the past. No freaking way. I do not want anyone to tell me, "Sorry, but due to hard drive bad sectors, invariably data corruption will eventually occur." I don't want to hear, "Every 5 years or so, you must delete your registers and start over because when you accumulate too many thousands of transactions, Quicken can't handle it anymore." I don't want to hear any other variety of lame excuses that attempt to blame the user, their hardware, their exact Quicken version (this problem is ubiquitous in ALL versions), etc. Quicken should be able to handle a register without errors when there are 500,000 transactions or 5,000,000 transactions. I only have 5,443 transactions - this should be a microscopic number for a 5GHz computer running on an M.2 solid state drive and 64GB RAM (on a 64-bit OS). There is no excuse for this to still be an issue, except that I'm guessing literally none of your coders actually reconcile their accounts when they use their own software (so they would never encounter this error when using their own software), which is unfortunate because basic business / recordkeeping (let alone accounting) teaches high school students that they should reconcile all accounts every month. Do your coders do that? This problem has been going on probably since the inception of Quicken. Please find the issue and fix it once and for all. Now that AI is at your disposal, there is no excuse for this bug to linger!! With the help of GPT 5.6, I'm quite convinced that even ****I**** could feed the code into it and find the bug myself, even though I'm not even a coder by profession!
@Chad115 it sounds like my Quicken usage is similar to yours.
But although our usage seems similar, I have never in all those years had reconciled transactions become unreconciled. So I wonder what could be different about our usages?
One thing I have done since 2020 when Q2017 online access sunsetted, is to always put my laptop into airplane mode before using Quicken. This ensures Quicken is not sending or receiving any data or updates from Quicken Inc. I also never used mobile, syncing to the Quicken cloud, or any of the transaction downloading methods that involve transactions being aggregated to Quicken's or Intuit's cloud. Can you think of any other differences in our usages?
One thing I noticed is that the date on the "Pure RV & Co" transaction also changed.
Changing the status of Clr to uncleared in the reconcile window by mistake is quite easy because it has a drag over toggle, but changing R to uncleared from the register by accident in Quicken Subscription is nearly impossible especially for multiple transactions. In past versions of Quicken you could click on the Clr column and it would toggle, but now you get:
And provided you have the "warn about changing reconcile" preference on even if you did that and then saved it, you would get this:
So, I think it is safe to say I would never "blame the user" for this kind of problem.
On the other hand, you are really going off track on your belief about what Quicken can and can't do, how easy it is to fix, and the underline cause. No one should be suggesting that Quicken can't handle anything smaller than about 32,000 transactions in a register, let alone some kind of timeframe for deleting. In fact, Quicken SuperUsers constantly suggest not deleting transactions when the user seems to feel they need to. But the number of transactions Quicken can handle in an account has nothing to with your CPU, disk space and such. It has more to do with the GUI controls and what variables are being used to track those transactions. For instance, if they use a 16-bit integer it can only handle +/-32,768. And that might have been the choice used in the database a long time ago to save space.
And you are way overestimating what AI can do to find problems in code.
But given that most people don't have this problem (like 99.9999% don't) I would guess at a data corruption problem. Now data corruption problems can be caused by all kinds of things, including code, but that isn't just going to pop out when looking at some code because the code in question would have done something at a time in the past that corrupted the data, and it might have been something external too, like opening/running your data file on a network drive that had a failure.
Have you tried Validate and Repair?
@Chris_QPW you said:
I had not noticed that. What do you think could cause the date change if the user is not changing the transaction? Cloud sync?
The only thing I can think of for this problem is some kind of data corruption. Nothing else really fits.
