Yep, still getting OL-220-A on Fidelity NetBenefits. Also updated to Ver R48.15, Build 126.96.36.199 today. Issue persists after this update.
I too am a victum of this error too. I've been unable to connect to my Fidelity account since late February.
Seems I have to correct more problems with this software since they went to an annual plan. After this recent membership purchase I don't see myself doing this again. Too much time correcting problems. Paying to beta test software? I don't think so. We're supposed to get paid to do that. LOL.
Same problems with connecting to NetBenefits (since 3/3/23). I agree with Scott. Overall product seems to be losing reliability. Connectivity issues, telling me my subscription expired when I just renewed, getting hung up and needing to use Task Manager.
I sent an e-mail to the CEO last evening. I got an update from him and he states that Fidelity has identified the change that they made on 3/7 that is causing the issue and that "Their current goal is 'to revert and test the changes with a target release of tomorrow, 3/22, at 9 PM EST’.
It sounds like they are finally making some progress on the issue
Fidelity Net Benefits OL-220-A going on for almost 2 weeks and counting…What's the problem, Quicken? Why isn't this resolved yet?
I've been using Quicken for over 25 years. I don't ever remember a version that was free of major bugs. More rapid decline though in the last few years. Quicken has some serious issues that would easily be fixed by checksums and standard things like that in the programming. I really don't understand why the software is so bad. At this point I'm looking for recommendations on alternate software or online options. I don't see any urgency on Quicken's part to resolve problems. Don't they understand I have bills to pay? Fortunately I did my taxes before the Fidelity Net Benefits OL-220-A thing hit.
Fidelity Net benefity adds a 'cash' data that effectively doubles the value of all retirement accounts. Does anyone have a work around?
Quicken users cannot effectively contact Fidelity about their patently failed "Data security with third-party websites and apps" rollout - as per: nb.fidelity.com/public/nb/default/resourceslibrary_redesign/articles/datasecurity
This is just another issue with Quicken, of many, over the past few years. It seems to be getting worse rather than better. I have used Quicken for 20+ years and the past year or so has just gotten more and more fustrating. One of my Finanicial Advisors who has been a Quicken user for more years than me told me he has now totally stopped using Quicken! I think maybe he has made the correct decision. I started using Quicken when Microsoft discontinued the old M/S Money program. I sure miss that program, It may not be as fancy as Quicken trys to be, but it always worked!
Customer Service and Engineering are not always on the same page for a variety of reasons.
Additionally, while I'm annoyed just like everyone else, I'm not seeing how this is an end-of-world problem. Perhaps people are day-trading their retirment accounts, but for me it's simply a few transactions every couple of weeks. So far, I'm just typing them in manually and I'm all good. One day it will be fixed and I can save those 10 minutes.
I saw the respone from yestyerday stating that Fidelity hoped to have the problem resolved by 9:00 ET today. I just tried (9:30 ET), and I am still getting ther OL220-A error. Chatted with Fidelity, but the technician new nothing other than to point me to this thread. I'm not sure this is a Quicken problem. Working in IT, I understand how third party changes can break software.
I certainly hope they have it resolved soon, it's been happening for a number of weeks now.