nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

No more transactions downloaded from Fidelity after 07/17/2026

Charles Brownmiller

Although my Fidelity accounts had various transactions after 07/17/2026, none of those were downloaded to Quicken (Windows 11), and no errors were posted.

Find more posts tagged with

Online Banking

Windows

Accounts

One Step Update

Comments

Quicken Carlos

Hi @Charles Brownmiller,

We appreciate you taking the time to post in the Quicken Community.

After reviewing my internal tools, I found the FDP-350 error. This error occurs when your security token has expired, and you need to re-enter your account credentials. Before you try any of the following troubleshooting steps, I recommend creating a backup of your data file.

Once the backup file has been created, I suggest deactivating and reactivating the account:

To deactivate an account:

Select the Tools menu and select Account List.
In the Account List, select the account you want to deactivate, and then click Edit.
In the Account Details window, click the Online Services tab.
Click Deactivate next to the service you want to disable.

Click Yes to confirm that you want to disable this service.

To reactivate the account:

Go to Tools > Add Account.
Select the financial institution for the deactivated account.
If prompted, select the connection method.
Enter your credentials and click Connect.
When the list of located accounts appears, choose LINK next to each account you want to reactivate.

Click Next, then Done on the last prompt.

I hope this helps. Let me know how it goes!

Quicken Carlos

Hi @Charles Brownmiller,

I just wanted to follow up since I haven’t heard back from you. I’m checking in to see if you still need assistance.

Charles Brownmiller

Thanks. Deactivating and reactivating fixed the problem. But why does this continue to happen?

It is not frequent, but often enough to be a pain. And, I got no warning at all. No errors. No notification. Just no updated transactions.

Quicken Carlos

Hi @Charles Brownmiller,

Thank you for taking the time to update the Community thread. I’m glad to hear that the steps above helped resolve the issue.

After you successfully sign in, a secure token is passed to Quicken and stored by the aggregation service. If the token expires, you may need to follow the steps above again to reauthorize the account.

To help us better understand what you’re experiencing, could you let me know how often you need to reauthorize the account in Quicken?

I look forward to your reply!

Charles Brownmiller

I don't specifically remember the last time I had to reauthorize the connection. But, there were other issues within the last year that required the reauthorization, so it may have been then.

While I'm sure that Fidelity and/or Quicken have good reasons for letting a secure token expire, from a user's standpoint this does not make sense. I shouldn't have to redo this if nothing else has changed. I don't have to reauthorize my credit and debit cards as long as I use them occasionally. It sounds like Fidelity or Quicken is just passing the task onto the user.

Quicken Carlos

Hi @Charles Brownmiller,

Thanks for sharing your thoughts. I completely understand your point. Having to reauthorize the connection when nothing has changed with the account can certainly be frustrating and inconvenient.

When the secure connection requires reauthorization, completing that process is necessary to restore the connection. Unfortunately, there isn't a way for us to prevent or bypass that requirement when it occurs.

If you find that the secure connection is expiring frequently, such as twice a month, please let us know.

We're happy to help!