nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

sync messing up split categories on bills and income

rskurato

I started to notice this the past few weeks. Everytime I sync with the cloud my split categories of my paycheck I schedule in Bills and Income get rearranged, and sometimes the values get put into the wrong categories. I tried reverting to previous software versions (currently 66.23, tried .18 and .12), no luck. I tried editing the order in the cloud version, and then I found that after saving when I reopened it in cloud (did not sync with my desktop version) the order was again messed up.

So, I thought the issue could be a corrupt cloud file, reset it, same issue. It is not related to a software update, it is not my file, something in the cloud version is reordering these and as a result, I cannot safely sync files. Anyone having a similar issue and is there any resolution?

Find more posts tagged with

Windows

Comments

Quicken Kristina

Hello @rskurato,

Thank you for reaching out! To help troubleshoot, please provide more information:

Is there anything that triggers this behavior?
- For example, if you manually correct it, does the problem return after a specific action, like running One Step Update?
Do you keep your Quicken file directly on your local hard drive?
Is it synced to any cloud service, such as OneDrive, iCloud, or Dropbox?

Have you tried making a backup of your file, then deleting and recreating the paycheck reminder?

These steps shared in an earlier discussion may also help:

https://community.quicken.com/discussion/comment/20513878#Comment_20513878

Please let me know how it goes!

rskurato

Anytime I access the cloud and make changes to Bill and Income split categories, even if I fix and save online, it gets messed up.

I reset cloud data (but not the full delete described here), no change.

My file is kept locally, not using online backups but I make local backups.

I deleted the recurring income reminder and made sure it was purged from the cloud and made a new one from scratch in the desktop software, it has the same problem.

Every time I sync to cloud, it gets messed up on my desktop program.

I turned off "sync with quicken mobile" on one step updates as well as sync when I exit, it still messes up.

Latest test, I turned of sync with mobile completely, to see if that messes up. So far it has not.

The issue has been going on for a few weeks only, possibly started around the same time as the Fidelity CC-601 error, which started after March 4th. I rolled back software and no difference, so it is an error with online.

With sync off on my desktop program, restarting the program and one step update, problem so far has not repeated itself.

Will try super validation and full delete of cloud data, but at this point it looks like this is an issue created around the same time as the latest Fidelity bug, really need both of those fixed.

rskurato

Ok, tried super validate, note, make sure you have room on the drive you do this on for 2x file size or it locks. Validation worked with no errors.

Went to reset mobile again, and again, without syncing, it messed up categories and reassigned them randomly. I see nothing else I can do, you need to see what you guys messed up and fix.

markus1957

As time has passed and more information has been gathered on this issue, it is clear that until a permanent fix is issued, the actions above will only work temporarily at best. 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, leave Sync Off and 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.