Fidelity Transactions NOT downloading

Olaf: I use Quicken Deluxe (latest client Windows version) and have 10 brokerage accounts at Fidelity Investments with a single Web Fidelity log-on, and 10 matching accounts in Quicken. I use quicken to download Fidelity transactions on a daily basis.  Quicken and Fidelity have recently established a new transaction download protocol via a Intuit-owned link-connection interface named "Express Web Connect +" that uses the OATH/Token protocol.  This link often breaks without error display or other warning. In addition, the relink process is not defined, is not reliable, and relink success or failure is not displayed.  The user can think everything is fine, but after a reauthorization and re-linking that appeared successful, transactions still do not download, again with no error display.  This is very frustrating as the vendor reauthorization and re-linking process in Quicken TAKES A LONG TIME and when not successful the complete process needs to be repeated in the hope that "this time it will work".

Olaf: Question:   What is a reliable follow-on process and steps to re-establish the "Fidelity Investments transaction download link to Quicken"?  Be sure at the beginning to include  steps and reasons to: (1) Refresh Sign in, then (2) Reset Cloud Data.

Gemini: Re-establishing a reliable connection with Fidelity after the transition to Express Web Connect+ (EWC+) can be exceptionally finicky because the "token" that authorizes Quicken to talk to Fidelity often gets "stuck" or out of sync between your local data file and Quicken’s cloud servers.

To fix this, you must perform a "deep clean" of the connection data. Following these steps in this specific order is the most reliable way to clear out the "ghost" settings that cause the silent download failures you are describing.

Step 1: Refresh Sign In

Reason: This forces Quicken to refresh your Quicken ID registration token. If this token is stale, it can't properly negotiate the OAUTH/Token handshake with Fidelity, leading to successful-looking logins that don't actually pass data.

1. Go to Edit > Preferences.
2. Select Quicken ID & Cloud accounts on the left.
3. Click Sign in as a different user (this is effectively a "Sign Out" button).
4. Type yes to confirm and sign out.
5. Quicken will prompt you to sign back in. Use your existing Quicken ID and password.

Step 2: Reset Cloud Data

Reason: Quicken uses a "Cloud Dataset" to manage EWC+ connections. If there is a mismatch between your local file and the cloud (which happens often when a link "breaks"), Quicken may think it’s connected when it isn't. Resetting the cloud data wipes the cloud's memory of your bank links so you can start fresh.

1. Go to Edit > Preferences > Mobile & Web.
2. Click Reset your cloud data.
3. Follow the prompts to complete the reset. This does not delete your transactions; it only clears the sync and connection metadata.

Step 3: The "Deep Clean" Re-Link Process

After refreshing your ID and the Cloud, follow these steps to re-establish the Fidelity link. Crucial: You must deactivate all 10 Fidelity accounts before trying to reconnect any of them.

A. Deactivate All Fidelity Accounts

1. Go to Tools > Account List.
2. Check Show hidden accounts at the bottom left (important in case a "ghost" account is hogging the connection).
3. For every Fidelity account, click Edit > Online Services tab > Deactivate.
4. Switch to the General tab and delete the "Financial Institution" name and "Account Number" fields. (This ensures Quicken doesn't try to use old, cached ID info).
5. Click OK and repeat for all 10 accounts.

B. Revoke Access at Fidelity (External)

1. Log into the Fidelity website directly.
2. Go to Profile > Security > External Data Sharing.
3. Find Quicken (or "Intuit") and Revoke or Remove access. This clears the token from the bank's side so a brand-new one can be generated.

C. Reconnect and Link

1. In Quicken, go to Tools > Add Account.
2. Search for Fidelity Investments.
3. Follow the prompts to log in. This will open your web browser for the OAUTH/Token authorization.
4. Crucial: On the Fidelity authorization page, make sure all 10 accounts are checked.
5. Once redirected back to Quicken, you will see a list of accounts. Do not click "Add".
6. In the Action column for each account, click the dropdown and select Link to existing account.
7. Carefully match each Fidelity account to its corresponding Quicken account name.

Summary Table: Why it fails.

I have tried all the above steps and even got on a chat session where the Tech walked me through creating a copy of the quicken file. After opening and adding Fidelity/Link to existing accounts, everything appears fine, I see all of my transactions. However, I suddenly see all of my transfers in and out of the brokerage accounts now shown as an FCASH security so I can't balance. I'm going through and deleting these transactions to see if I can pull down the original transfers.

After talking to support and going through the steps to create a copy of my Quicken file, I can connect to Fidelity, and I can now successfully download transactions. However, whatever fixed it introduced a new problem. Quicken now considers any cash transfers in or out as belonging to an FCASH security. Where before, I would see on the Investing page a node for Fidelity and under that node, a 'stock' node and a cash entry.

Now, I see the stock node, an FCASH node, and a cash entry. For some reason, it has created a 'CASH' security and transactions that come in for cash (Dividends, transfer out) keep getting interpreted as a security Deposit or Sold. Worse, I see the dividend and transfer out transactions AND a matching CASH Deposit/Sold transaction. I can't figure out how to stop this behavior and only way to actually reconcile is to keep deleting these FCASH transactions.

I've gone through the 'copy' steps multiple times but as soon as I complete connecting to Fidelity, the FCASH security is created.

[Edited-Readability]

Now that Quicken/Fidelity is "up and running" and the Gemini re-link process is known, I hope Quicken Development will recognize as a "Priority 1 Bug" that "One Step Update", and similarly individual account "Update Transactions", does not have functionality to report to the user: (1) a failed Express Web Connect + / OAUTH Token update (any reason), (2) a failed "re-link process" where the Gemini-described re-link steps "did not work/succeed" (any reason). If additional code is needed to detect such failures in either the Intuit Express Web Connect + pipeline/link, and/or the Fidelity token-owner side, the Quicken please write and test that code. Allowing "One Step Update" and "Update Transactions" to run and "error-out" with no error-reporting to the user is unconscionable.

Also re: means of error reporting, if such failure is a "601 Error" then the 601 error should be reported-out to the user, regardless if the 601 error cause is the one that is currently reported out to external/users, or if the error source is the separate 601 error source (same effect) that is now only reported INTERNALLY and only able to be seen by "Quicken Support Supervisors. The 601 error should also explain that the link is "broken", requiring a repeat of the Gemini re-link process.

thanks, unfortunately this did not work for me :(