Sync to Web Constantly Corrupts Scheduled Transactions with Splits

dayjk88
dayjk88 Quicken Windows Subscription Member

Windows 11, Desktop. Routinely (I mean at least weekly and sometimes multiple times a day) when syncing to mobile/web scheduled transactions with splits are corrupted. The split amounts remain correct but the categories and memo fields get shifted around (and sometimes a single split memo field gets duplicated across all split lines) to different rows. I can run a validate, do a mobile sync, and then immediately run validate again and get notified of scheduled transactions that were "corrected" - at which point I look at them in the desktop and they have been corrupted. I also notice that it reorders the split lines, which is annoying but doesn't affect the integrity if my data, although I suspect that behavior is part of the problem. This has been happening for months and I finally figured out that it is the sync process that is causing this. This is quite disheartening as it is defeating the entire purpose of splits and category tracking and making the mobile sync pretty much useless. Clearly this has been a bug for some time, and searching the community forums I see other have reported this as well. This needs to be corrected. This does not represent the quality I have come to expect as a dedicated Quicken user for at least 20 years.

I did a complete reset of the web data yesterday, and 3 times this morning this has occurred again. Quicken support, please don't tell me to reset my web data and try again.

Currently R66.23 Build 27.1.66.23

Comments

  • markus1957
    markus1957 Quicken Windows Subscription SuperUser, Windows Beta Beta

    I have it on good authority that Quicken is working on the issue. The R66 release implemented a fix that prevents the issue when Sync is turned Off. I also recommend before turning sync off, deselect cloud sync from One Step Update settings. Then after validating your file and restoring any jumbled reminder splits, wait for a full fix to be implemented. It's frustrating that the full value of the product cannot be utilized but that is where the issue stands.