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; } } }

ONE STEP UPDATE

Jayacol

One step update keeps going forever never completes the only way to use Quicken is with task manager and end task.
This has been happening for about a week or so now.
tried all the usual fixes mentioned on other posts by people having the same problem.
its obliviously a quicken problem and not my computer or data file.

Find more posts tagged with

Comments

splasher

Contact Quicken Support

Canary#9Bm

I just had the same problem!

jdcq

I'm having the same issue after updating Quicken. I usually wait a while before updating, but I didn't wait enough this time — See https://community.quicken.com/discussion/7924596/issue-with-one-step-update.

I also found a similar issue from 2020:
https://community.quicken.com/discussion/7868656/cloud-sync-not-completing-and-gets-stuck-on-downloading-transaction-edited-for-readability

What works for me right now is to disable cloud sync. Obviously, this is not a permanent solution...

Resetting cloud data does not work (and takes a very long time).

Boatnmaniac

For me OSU times have significantly increased in the last couple of weeks. What used to take 1.5-2.5 minutes to complete at first extended to 2.5-3.5 minutes about a month ago but in the last couple of weeks it is now taking 7-10 minutes to complete in my main data file.

I have 11 accounts (with 4 finanancial institution setups) that are connected with DC. And I have 9 accounts (with 7 financial institution setups) that are connected with EWC/EWC+. The DC accounts update very quickly with no noticeable delays. It is the EWC/EWC+ accounts that are the driver of this issue so something sure seems to be amiss with either Quicken's and/or Intuit's servers.

As bad as this situation is it is not as bad as when it happened the last time (1.5-2 yrs ago) when the connection channel was transitioning from FDS to QCS. Then there were people who said it was taking as much as an hour or even a little longer for OSU to complete.

I would caution people to avoid force closing Quicken if possible because there is risk of causing data corruption by doing that. Maybe give OSU more time to see if it will complete running.

I have also found that limiting OSU to just the DC accounts and then doing Update Now for each of the EWC/EWC+ financial institutions individually does speed up the entire updating process. Certainly not ideal to do it that way but it is saving me some time.

jdcq said:

I'm having the same issue after updating Quicken. I usually wait a while before updating, but I didn't wait enough this time — See https://community.quicken.com/discussion/7924596/issue-with-one-step-update.

I also found a similar issue from 2020:
https://community.quicken.com/discussion/7868656/cloud-sync-not-completing-and-gets-stuck-on-downloading-transaction-edited-for-readability

What works for me right now is to disable cloud sync. Obviously, this is not a permanent solution...

Resetting cloud data does not work (and takes a very long time).

Thanks for passing along that disabling cloud sync has helped you. Cloud sync should only be enabled if one is using Quicken Mobile and/or Quicken on the Web to prevent possible cloud account issues.

You also mentioned that resetting the cloud account did not work. Did you try deleting the cloud account? Or how about signing in as a different user? If so, what was the result?

jdcq

I did not try deleting the cloud account. I did try signing in as a different user.

I may have gotten things working a little better by:
1. Turn off Cloud Sync.
2. Turn on Cloud Sync. Disable all accounts. Reset cloud data.
3. Enable accounts incrementally. Testing OSU (w/o Cloud Sync) after each add.
4. Cloud Sync.

Unfortunately, I now have some data corruption

jdcq

I reverted to a backup and repeated the process. I was lazy and enabled all accounts at once instead of incrementally - This resulted in a ~50 minute OSU.

When I retried the process (with incremental enabling) on another install, OSU is reasonable in duration.