Looking for any update on this problem
Thank you for the follow-up,
The issue is still open and ongoing. Since the financial institution has not stated an intention to stop supporting Quicken, I assume it should be fixed in the future. We do not have an ETA.
Thank you!
Thank you for your reply,
The 409 conflict error you're seeing in the logs is helpful. Please backup your Quicken file, then follow these steps based on our article on 409 conflict errors:
Please let me know how it goes!
I'm glad to hear that all 5 accounts are updating!
If you need further assistance, please feel free to reach out!
It appears to be only a temporary fix, the next time I do a One-Step-Update from the home page it just updates the same three accounts.
To help troubleshoot the 2 problem accounts, please provide more information:
Also I see the following error (409) during the "Reset account" time frame, but NOT during the early One-Step-Update time frame, which is strange because it updates all account from the "Reset accounts".
<!-- ***** RECV from https://services.quicken.com/institution-logins at 09:51:59 on 20260223 ***** -->
{"items":[{"code":409,"resource":{"status":"ERROR"},"errors":[{"title":"Conflict detected. institution-logins [522006771649981440] has a conflicting attribute [name=Credentials, answerValue=null].","httpStatus":409,"code":"QCS-0409","extData":{"attributeName":"Credentials","conflictId":"522006771649981440","conflictClientId":"81ACD660-E082-43A9-BEE0-066EC9D94B23"}}]}]}
I just did some research on the QCS0409 error and looks like it's just related to Quicken for MAC, I am using Windows. I did use a MAC, but that was about 3 to 4 years ago. So don't know what that means.
Thanks for your help.
Hello Kristina, initial results are GOOD!! followed your instruction and look at the results, show "5 accounts updated under MidFirst and it was way faster!! The Log shows NO 409 error. I will update you Tuesday morning after I do the One-Step-Update, I should have several transactions to download then. Thanks!!
I'm glad to hear that so far, it looks good!
Please let me know how it goes on Tuesday!
Good morning, and yes, it is a GOOD morning, it worked perfectly all 5 accounts for MidFirst updated!! Thank you, Kristina for all your help and patience getting my problem fixed. You provided real customer service, thanks again and have a good day.
Well everything worked great for a week maybe a week and half, then the morning of March 2 it failed to update the 5 MidFirst accounts, giving me the CC-601 error, then it worked that afternoon. This morning got the same CC-601 failure, tried this afternoon and got the same error. Any Ideas??
Unfortunately, it's a widespread issue affecting more than one financial institution. It has been reported to our Development and Product teams for further investigation and resolution. Though we do not currently have an ETA, you can bookmark the Community Alert linked below to be notified of updates and to know when the issue is resolved:
(Ticket #12269329/ CTP-16510)
Looks like the software update from yesterday fixed this problem, it's work fine yesterday after installing the patch and it worked fine today. Thanks!!
I'm glad to hear it's working again!