Reporting this now. Been down since maybe 11PM EDT yesterday. Still down at 6:30 AM. Likely will resolve, but thought the community should know.
Hi @Bob.,
Thank you for sharing the error you encountered. According to our support article, this error typically occurs when Quicken’s financial data platform (FDP) is unable to connect to your bank to retrieve recent transaction information, usually due to an issue on the bank’s end.
In most cases, the issue should resolve within 24 hours. If you continue to experience the error after that time, please let us know, and we’ll be happy to assist further.
Thank you!
Fully aware of that, but thanks. Sometimes, that is NOT the case. So i felt worth mentioning if someone @quicken wanted to check or if someone who has not seen that before was surprised and checking here for the error. This could be Fidelity and could be the aggregator.
OK, this has been down since Friday night and still as the business day starts on Monday. Reported to Quicken twice. Please help if you can.
Absolutely brilliant AI bot when I called. Knew I had reported the issue specifically before i said a word, said widespread and know and they are working on it. Literally the best non-human phone bot i have ever encountered. I never once had to scream "agent"!!
Thank you for letting me know. I verified the error you’re experiencing.
This was previously a known issue that affected multiple users across different financial institutions, but it has since been resolved. As a result, the error you’re currently seeing does not appear to be related to that known issue.
Given the nature of the error, I recommend contacting Quicken Support and speaking with a live agent. They can further investigate the issue, provide troubleshooting assistance, and escalate your case if necessary.
You can find the Quicken Support phone number here: Support Home | Quicken. Phone support is available Monday through Friday, from 5:00 AM PT to 5:00 PM PT.
I apologize that I could not provide a more direct solution, but please don’t hesitate to reach out again if you have any other questions.
Read the above. Already called @Quicken Laura And check with support. This one IS a known issue.
Now down 4 days. Reported multiple times to Support. they know about the issue and i am surprised it is taking this long to fix. Concerning.
I’m sorry to hear the issue is still persisting. As I mentioned previously, this is not currently an ongoing issue, so we’ll need to look into the specifics of your individual case.
You mentioned that you’ve reported this issue to Support multiple times. To clarify, by “reported to Support,” I mean speaking directly with a live agent and reporting the issue to them, rather than only submitting your log files. Typically, when you speak with a live agent, a support ticket is created. However, I don’t see a recent support ticket associated with this issue.
If you haven’t already spoken with a live agent, I recommend contacting Support and speaking directly with a representative so they can review your specific case and determine the appropriate next steps.
If you’ve already spoken with a live agent, please provide me with your ticket number, and I’ll be happy to check on the status of your case.
Thank you for your cooperation. I look forward to hearing from you.
@Quicken Laura are you new? I fear you are not reading before hitting cut and paste!
Absolutely brilliant AI bot when I called. Knew I had reported the issue specifically before i said a word, said widespread and known and they are working on it. Literally the best non-human phone bot i have ever encountered. I never once had to scream "agent"!!
That sure says to me they know about the issue and I do not need to call. Why don't you check and if they have no idea that Fidelity Investments is going 2505, I'd be happy to call anyone you like. But when I call, they say we recognize the phone number and you have reported Fidelity Investments 2505 - is this what you are calling about? Then I think they know.
Hi @Bob.
I apologize for the confusion with the AI bot, and I appreciate you taking the time to attempt to contact Support. I’ve passed your feedback along internally for review.
Regarding Error FDP-2505, I can see that you’re still receiving the error today. I’ll gather the log files you’ve already submitted and create an escalation ticket.
Please keep an eye on your email, as the escalation team may reach out if they need any additional information.
I hope this helps, and thank you again for your patience and cooperation!
[CBT-1249]
Thanks @Quicken Laura I think we are on the same page now, except the bot says "widespread and known" and no one else has posted here about it best I can tell. Happy to help out at any time. And yes, still an issue. 5 days is unusual for these errors.
@Quicken Laura I have also been experiencing this issue. First noticed it Tuesday 8/18.
@Bob. FWIW, I just right-clicked one of my Fidelity accounts, chose Account Settings, went to the Downloads tab, and clicked the Update Login button. Followed the directions there, and all Fidelity accounts are updating again.
[Edited - Readability]
Hi @seanfremouw,
That’s great news! I’m glad to hear everything is working again. Thank you for sharing the steps that helped you update your accounts successfully. I’m sure they’ll be helpful to other community users as well.
If you have any additional questions, please don’t hesitate to reach out.
Brilliant call @seanfremouw ! I had to be careful as Quicken/Fidelity wanted to bring in my Visa card as well as a new account but I get my balances and transactions there from Elan, so had to uncheck that, and be sure to use LINK to existing for the brokerages. Surprised Quicken support has not figured this out and posted. The error they present is clearly not for this issue. If it had been a reauth message I would have fixed this days ago.
THANKS!
@seanfremouw Thank you for posting this! I have been experiencing the same issue/error message for all my Fidelity accounts and was about to start posting/calling support/etc. That process resolved the issue.
Solution for me: (Part 2 newer) OK – in my case quicken login to Merril said access denied. So I tried to independently login into Merrill and I got the message. - you have not logged in in a while. Let's create a new password. So I did that and created a new password and was able to login to Merrill again. Then I went back to quicken and updated my login and now everything worked because it was not access denied and I was able to re-link my existing account accounts. Just passing that on if it helps anyone.
Care Code: access_denied
Details: User Access Denied: Access Denied, Connecting with partnerUid: bofa_fdx_merrill_prod for intuitProperty: quicken, intuitUserId: xxx, intuitRealmId: xxx on user authorization, error_code: access_denied
