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 Still Frozen — Outage NOT Resolved (Technical Details Included)

Larry Jones

The outage is not resolved. I’m providing exact technical symptoms so engineering can see what’s actually happening on the client side.

Environment:
Quicken Classic Deluxe (Windows)
Latest R‑release
Multiple institutions enabled for OSU

Symptoms:

One Step Update window opens normally
All institutions appear in the list
Every institution remains stuck at “Waiting…”
No transitions to “Connecting…”, “Processing…”, or “Complete”
No error messages
No timeouts
The OSU window cannot be canceled
Quicken must be force‑closed
After restart, First Horizon still shows zzz‑First Horizon (metadata not refreshed)

What this indicates:
This is not a local file issue, not a bank issue, and not a user configuration issue.
This is the signature of a partial aggregator recovery failure:

The aggregator is accepting the initial OSU request
The backend is not executing any institution calls
The callback queue is not returning status updates
Metadata refresh has not propagated
Worker processes appear offline or jammed
Routing layer is non‑responsive

If even one institution were healthy, OSU would transition to “Connecting…” for that institution.
None do.

This is a backend freeze, not a client‑side problem.

Request:
Please escalate to the aggregator engineering team.
The outage is not resolved from the client perspective, and OSU remains non‑functional for all institutions.

Happy to provide logs if needed.

Find more posts tagged with

One Step Update

Sync Error

Comments

markus1957

ZZZ accounts are not valid FIs. they are usually transitioning to a new connection or being dropped.

Agree though that this is a back-end issue generically when EWC/EWC+ accounts do not respond or at least not in an anticipated fashion. Usually, OSU will time-out and present the OSU Summary screen with a generic error, but it can take 10 minutes. There should be a generic timeout of a couple of minutes.

Larry Jones

Thanks — agreed on all points. The behavior I’m seeing matches a backend freeze rather than a normal outage.

Key differences:

OSU never transitions from “Waiting…” to “Connecting…” for any institution
No timeouts occur, even after extended waits
OSU cannot be canceled
Quicken must be force‑closed
Metadata for First Horizon remains zzz‑First Horizon after restart
No institution returns status updates, errors, or callbacks

This is the signature of a callback/worker‑pool failure where the aggregator accepts the initial OSU request but does not execute any institution calls and does not return timeout signals.

In normal outages, OSU eventually produces a summary screen.
Here, it produces nothing at all.

This is why I’m reporting it as “not resolved” — the backend is still non‑responsive.

Larry Jones

Ok, just for giggles, I created a new, blank test file. I tried to add First Horizon. I enter my credentials. It tries to connect, then throws "Please complete your enrollment process to proceed." That strongly looks like the backend aggregator is still having issues.