Trouble downloading transactions from Fidelity

MarkTwain

My Fidelity is finally working again as well, but I needed to deactivate and then reactivate online services to get it to work.

brooksrs@

I have tried Resetting and Deactivating/Activating my Fidelity Investment online services (I have 3 accounts). I even went back to a Nov. 2024 backup and it worked once for 2 of the accounts but not at all for the other. They originally stopped working in Dec 2024. They work sporadically but at this time not at all.

Quicken Deluxe Version R61.20 Build 27.1.61.20

Racerboy80

Where is everybody at on this? Mine remedied itself and now I'm back to not syncing. I've disabled and re-enabled all accounts and the problem persists.

ray626

I have 2 connections to Fidelity. Yesterday one updated and one didn't. Today neither will update with no explanation other than "Your financial institution has rejected this transaction."

Jim_Harman

My Fidelity downloads also failed today.

The error message is OL292-A "Your financial institution has rejected this transaction"

MSStateDawg

https://community.quicken.com/discussion/comment/20484900#Comment_20484900

Same.

This morning is the first time I've had an issue.

Charles Farnell

I also have 20+ years of data in Quicken for Fidelity. I hate to tell you but this issue crops up all the time. It will work for a while and then stop working for no reason. I am currently 2 weeks in (first 2 weeks of April 2025) and have no successful syncs. Having posted and studied this over the years I think the issue is on the Fidelity side and its related to volume and them throttling the load at certain times.

Try Sundays 10-11 ET, that normally works for me, although did not this past Sunday 4/13.

It is very frustrating and I would ditch Quicken for an alternative, but have not found anything better just yet.

DRH3564

Hi, Charles,
As the originator of this thread, I can say the same thing. Lately the sync with Fidelity has been working, and then today, it did not.
I did find that creating an new file just for Fidelity accounts resolved the matter. But then you can't transfer funds back and forth to/from your Fidelity accounts and other accounts, and you lose your pricing history, etc.
Hopefully, one day Fidelity will resolve the matter.

DerekG

I'm having the same issue with Fidelity and the same 'an error has occurred' message. Been happening for at least a week, maybe two. It was working fine last month, and all other institutions are working just fine. I'll try de-activating it and re-activating it tomorrow but I have about 10 accounts and I'd rather not do it one by one. Is there a way to do it one time across all 10 accounts? I don't want to have to remap every account at Fidelity to the ones in Quicken if at all possible!!

Boatnmaniac

@DerekG -

Is there a way to do it one time across all 10 accounts?

Deactivating can only be done one account at a time. After deactivating, go to Add Account and select Fidelity Investments. That should reconnect all of the Fidelity accounts at one time.

This is generally the preferred process when doing deactivate/reactivate. When there are multiple accounts involved we often do not know which account(s) might be causing the issue. It's often best to deactivate all of them and then do Add Account which gives it a totally clean slate. And generally it's also faster to do it this way than to do one account at a time.

I don't want to have to remap every account at Fidelity to the ones in Quicken if at all possible!!

Unfortunately, that is not something we can control. Sometimes the mapping of the downloaded data matches up perfectly with the accounts that are already in Quicken. Other times, we need to Link the downloads to the correct accounts. I think it has to do with whether the download connection issue being experienced is because the financial institution made some system or other change that affects the downloaded data. When that happens, the remapping needs to be done. When that does not happen then it seems that Quicken does the mapping correctly all by itself.

KyleL

I'm still getting the error.

OL-220-A

Last successful update was 4/13