This discussion was created from comments split from: New VOYA and Quicken Issues.
Two of my Voya Retirement Accounts went down over the weekend with the inability to download data. No Bill Pay involved. OL-293-A is occurring. It's been more than 72 hours. It says unexpected information was received from your financial institution.
Exact same issue here as well starting about 4 days ago. Error OL-293-A. I got an email from Voya today bragging on the updates they have made to their web site, so presuming that in the process, they broke the Quicken downloading. Bummer.
Exact same issue here as well starting about 4 days ago. Error OL-293-A
Hello @Monte Bliss & @schoonpsu,
Thank you for taking the time to visit the Community to report this issue, though we apologize that you are experiencing this.
I forwarded this issue to the proper channels to be further investigated. In the meantime, please navigate to Help > Report a problem and submit a problem report with log files attached and (if you are willing) a sanitized copy of your data file in order to contribute to the investigation.
While you will not receive a response through this submission, these reports will help our teams in further investigating the issue. The more problem reports we receive, the better.
If you haven't already done so, I also recommend following the troubleshooting in the article on OL-293 errors linked below: https://www.quicken.com/support/error-when-using-quicken-online-services-ol-293-or-ol-294/#section-windows-1
We apologize for any inconvenience! Thank you.
(CTP-17849)
I would like to report that I am also experiencing this problem as well. It started when I tried to update my account on Saturday July 18. One thing I would like to add is that when I tried logging into my account on the Voya website the site was down for maintenance. On Monday July 20, the website works but Quicken still does not.
Same issue as described. Well said.
What Daniel said!
same issue as previous posters
same issue here as well.
I'm Having the same issues as well
Exact same issues here. The problems began July 18 and are unresolved and un acknowledged at both ends (Voya and Quicken).
I'm having same issue
Same Issue BTW; tried reset-NG, Tried deactivate and reactivate - NG.
Report Submitted.
Subject (CBT-1210)
Thank you for your replies,
I added all of you to the ticket to ensure our teams are aware you're encountering this issue. Thank you to those who sent a problem report with log files attached. It will help our teams investigate the issue!
Thank you!
I just called Voya - They know nothing they said. Same exact issue here. I cannot download anything
Gina
Hello @Gina Santacroce,
Thank you for letting us know you're encountering this issue! If you would like to contribute to the investigation, please navigate to Help>Report a Problem and send a problem report with log files attached.
If you send a problem report, please post to this discussion to let me know, so I can forward it to our teams!
Good evening. Reporting that I am encountering the same issue with Voya (OL-293-A). Last successful sync was on Friday 7/17/26. No success since their maintenance. I submitted a problem report from Quicken with associated log files.
Same issue since after my last good download which was 16 July 2027.
Reported Problem thru software.
kinda annoying now.
It has happened in the past, and now again. Last connection was July 16, 2026.
Usually seems to take a few weeks to resolve - I'm convinced that that only happens when the Quicken team admits that the problem is on their side and they buckle down and fix it.
Same here for the same time frame. I haven't seen any updates to the issue. Let's go Quicken get the connection back up…
"Quicken Kristina", you can add me as well.. I just reported the problem and sent in the logs that were check marked.
Me too. I submitted the problem via the Quicken Help menu option.
Thank you for submitting your logs @ronedog.
We've added your log files to the open case for further review.
Thank you @James White.
Same here, I have a Voya ticket open on it, took some doing.
Hi @SomeItalianGuy,
I've merged your post into this ongoing thread since your issue appears to be related.
When you have a chance, could you please submit your log files and include the error code you're encountering? This will allow us to forward the information to the appropriate team for further investigation.
To send your logs:
Once submitted, please let me know. I look forward to your response!
Myself as well. Very frustrating that neither Quicken or Voya are even acknowledging the issue.
Hi everyone,
Thank you all for your reports.
We now have a Community Alert available that you can bookmark to stay up to date on this issue. We'll post any new information or progress there as soon as it becomes available:
Thank you for your patience and continued cooperation!
(Ticket #12516462)
Done.
Hi Kristina. Please add me to the list. I just reported through Quicken a few minutes ago and sent all available logs. Thanks.
I'm also getting the "OFX Error: 16503" error. please add me to the list. Also I have submitted the error directly from the Quicken Mac.
Hi Quicken Community,
I found this discussion by searching for what I believe is a similar issue with my wife's Voya accounts in Quicken. This OL-293-A issue started occurring about a week ago. I reached out to Voya, but they've not responded at the time of this post. Thanks in advance for any help or insights.
Thank you for letting us know you're encountering this issue! I have moved your post into an existing thread for the same issue.
This issue has been escalated and is currently being investigated. If you would like to contribute to the investigation, please navigate to Help>Report a Problem and send a problem report with log files attached.
If you send a problem report, please post to this discussion to let us know, and we will get it added to the ticket!
Yes same issue, it started after a recent upgrade on the Voya side, I have removed and tried to re-add my account details and yet it still does not work.
Thanks for chiming in, though I am sorry to hear that you have been affected by this as well!
This issue has been escalated internally for investigation. If you would like to aid in that investigation, you can do so by following the instructions in my previous post.
We apologize for any inconvenience this issue is causing.
@Quicken Alyssa Out of curiosity, is there a process you can provide for escalated investigations? Furthermore, is there a target date for the root cause investigation into this OL-293-A issue to be completed and corrective action(s) issued? It just seems that these issues seem to lag and there is a lack of transparency. Thank you in advance.
I have sent in a problem report. I know after the maintenance on Voya's side I had to re-recongize my computer when logging into Voya.
It's nice that the team is aware and investigating, but what is taking so long? It's been nine days since I was last able to download data for my investment accounts - I could be going broke for all I know! 😯
Please update us Quicken and Voya its been over a week almost two weeks. @Quicken Laura @Quicken Kristina
OL-293-A issue to be completed and corrective action(s) issued? There is this thread and another one booked marked that says it has been escalated. I can't get anything to work and calling Voya is useless. They just transfer you to Quicken and some of the techs haven't a clue to what we are talking about. Please help us get this straightened out. Thank you
Thank you for your reply,
The ticket is open and in work. No new updates are available.
It seems that we all have the same problem with Voya: Error code OL-293-A. Please provide any update regarding this. I'll also be reporting problem under Help heading.
same issue for me. Please add to the ticket. Sent the log in and reported it last week
AI Response>
Me: Do companies like Quicken and Voya use a data interchange/security protocal or standard when Quicken downloades the data from Voya? If there is a standard, who isn't following it since Voya does't connect since their "Maintenence" about 10-12 days ago.
Yes, there are established standards and protocols for this kind of data interchange.
The longstanding industry standard is OFX (Open Financial Exchange). It has been used since the late 1990s for financial software (including Quicken) to talk to banks, brokerages, and retirement plan providers.
Quicken supports several connection methods built around (or related to) OFX and newer approaches:
The industry is gradually moving toward the FDX (Financial Data Exchange) API standard. This is a modern, royalty-free, REST/JSON-style open banking API focused on secure, consumer-permissioned data sharing. Quicken’s EWC+ is closely aligned with FDX-style approaches. OFX is still widely used (especially for Direct Connect), but many institutions are migrating away from pure OFX toward FDX or similar API methods.
Security relies on HTTPS/TLS encryption for the data in transit, plus authentication (username/password, sometimes multi-factor or tokens). Credentials handling differs by method—Direct Connect keeps them more local to the OFX conversation; aggregation methods involve Quicken’s servers to varying degrees.
Voya Institutional Plan Services (the common one for retirement/401(k)/participant accounts) has a known, widespread connectivity break with Quicken. It started right after Voya performed website/maintenance/upgrades around mid-July 2026 (roughly 10–14 days before today). Users report errors such as:
Quicken has officially acknowledged the issue, escalated it internally, and is working with Voya. There is currently no ETA. Multiple community threads confirm the timeline matches Voya’s maintenance window and that the website itself is functional for normal logins.
Neither side is necessarily “refusing” a standard in a willful sense. These connections require ongoing coordination:
In practice, after a maintenance event like this, the break is almost always on the institution’s side first (server responses change, OFX endpoints behave differently, auth flows are updated, etc.). Quicken then has to diagnose the new responses and push a fix or configuration update. Quicken’s own notes on similar past cases (e.g., other large institutions dropping OFX) state that the financial institution decides the supported methods and Quicken follows them.
Voya has supported Direct Connect (OFX-based) for Institutional Plan Services in the past, along with other methods depending on the exact account/plan. The current failure (including HTTP-500 style errors) points to something on Voya’s end after their recent changes that Quicken’s existing connection logic no longer handles cleanly.
Lets goo Quicken Support!! What is happening with this??? Almost a week following the Community Alert on this issue and no updates. Quit keeping your paid customers in the dark!
