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; } } }

Update results are sporadic for some accounts

rfsinten

Windows 11; Quicken Version: R69.26, Build: 27.1.69.26

Anyone experiencing unreliable account updates using both One Step and Update Now (cntrl+alt+U)?

Accounts affected that I’ve detected include Regions bank and Bank of America. I have multiple accounts at each bank with seemingly complex update issues. It isn’t every account at a given institution that fails to update.

For Bank of America right now it is a Visa account that has failed to update since 8/26/2026 – this account uses Express Web Connect for its Connection Method. Other accounts at BofA update both with One Step and with Update Now, at least over the past couple of weeks. I was experiencing a similar problem with the checking account, but a Deactivate/Reactivate cycle (for all accounts) has fixed the problem except for the Visa account. For the Visa account, I get no error in the One Step Progress window or in the Summary window. Likewise with the Update Now single account update - Quicken does not notice the failure. I note that attempting to manually download a .qfx file that BofA recently disabled manual downloads in .qfx format and refers back to using Quicken update methods. Coincidence? A second note, my Merrill Lynch accounts seem unaffected by this issue, but they are all connected through the Deactivate/Reactivate cycles, i.e., BofA lists them in the share account list and Quicken links them all at the same time.

Regions is a little more nefarious. These accounts use the Direct Connect connection method. With the checking account, I regularly get “an error occurred” warning in the One Step Progress window, but the Summary window shows no error – I get the green shaded check mark. Then if I attempt an Update Now single account update it pretends everything is working and there were no records to download, so no error indication even though there are records to download. During the last few update sessions, I have run several Update Now cycles as I attempt various bug isolation events and I’ve noticed if I do three or so Update Now cycles, the account updates.

I do not know if these are separate isolated events or connected to an Update issue. I have accomplished Deactivate/Reactivate cycles for both institutions. Also, I suspect that this error may be affecting other accounts that do not have regular records to download (e.g., Comenity account for Dell).

Find more posts tagged with

Online Banking

Windows

Missing Transactions

Accepted answers

All comments

GTRMQuick

[Removed - Duplicate Post]

Quicken Kristina

Hello @rfsinten,

Thank you for letting us know you're encountering this issue. To help troubleshoot, please provide more information:

When did you first notice these issues?
- Did the issue with Regions and the issue with Bank of America start at the same time?
You mentioned that running Update Now multiple times gets the account to finally update. Is that only for the Regions account, or does this also apply to the problem account with Bank of America?

If you haven't already done so, please try following these steps from our article on missing transactions/transactions not downloading:

Be sure to follow these steps in order:

1. Go to Edit > Preferences > Downloaded Transactions. The option Automatically add to banking registers needs to be unchecked.

2. Refresh your online account information by clicking the Actions Gear Icon on the upper right of the register, and select Update Now. Follow the on-screen instructions to complete the update.

3. Confirm that the Sort Order in your account is by Date; just click the top of the Date column in your account register. It's possible the transactions are in your register, but not where you thought they'd be.

4. Click the Reset button at the top of the register. This will confirm that there's no filtering in your account register.

5. Try refreshing your login session: To do this, go to Help > Refresh Sign in. After completing the log-in process, trying running a One Step Update again.

6. Go to Actions (Gear Icon) > Register Columns > Check Downloaded Payee in the account register. This allows you to search by Payee to confirm the transactions haven't been renamed unexpectedly.

7. Go to Tools > Account List and check Show Hidden Accounts at the bottom left. Confirm the missing transactions haven't been added to a hidden account by clicking on the name of any account that appears with a check mark in the Hidden column.

I look forward to your reply!

rfsinten

First, thank you Kristina for your reply and advice.

I attempt to address each question and step in this reply, but let me know if I missed something,

I first started noticing these issues shortly after the Fidelity update troubles got resolved – I am reasonably sure these are not directly connected, but they seemed to occur after all of the migrations from the old connection methods to Express Web Connect +.

The issues with Regions and BofA started around the same time, but the issues manifest themselves differently and evolved as noted in the original post, so I did not initially correlate them.

The multiple Update Now sessions only works for Regions, but it works fairly consistently on that account.

As for the steps you suggested:

The Automatically add to banking registers check box was/is unchecked
No effect
Already sorted by date – that’s my default
I do not have a “Reset” button at the top of the register on any account. I do have the same filters as those shown in the screenshot, just not reset button.
No effect
No unexpected renames (though this is a useful feature and glad I learned it exists)
No hidden accounts, but that did make me think to check Separate accounts – no luck there, though

Number 7 revealed a curious data point. There is a column in the account listing labelled, “Last Download.” For the Regions and the BofA accounts the entry in this column is “Not Available.” However, for my investment accounts and at least most of my credit card accounts, the column contains today’s date because I performed a One Step Update today. Also, of note after the One Step Update, I did the Gear->Update Now step for Regions and the BofA Visa accounts, but the entry fis “Not Available.”

Dave335

I am Still running a stable version of 68.31 And waiting to hear that all the little bugs are out of this 69.** series before installing. I was curious about that reset button as I don't have it in my version either. Is that something that came out in 69.26 version?

Sceptic

@Dave335 the green rectangular Reset button at the top of the account register has been around for a while. I think since 2018, but not sure. It doesn't show up until you have done a search or filtered your account register. It is an easy way to restore your account register back to default settings.

Once you press "Reset", the button disappears,

Dave335

Thank you. I just tried what you said and there it was. I learned something new today!

Quicken Kristina

Thank you for your reply,

To clarify, does the Last Download column show "Not Available" exclusively for the problem accounts, or for all of the accounts with those financial institutions?

To check for possible file-specific issues, I suggest that you try validating your data file. Please save a backup file prior to performing these steps.

Validate:

File

Validate and Repair File...

Validate File

Click OK

Close the Data Log

Close Quicken (leave it closed for at least 5 secs)

Reopen Quicken and see if the issue persists.

Please let me know how it goes!

rfsinten

Today I focused on Regions. Several Update Now sessions with no downloaded records, even though there are updated records in the online bank registers. No errors indicated in the update progress or summary windows. This time multiple update now workflows did not result in an actual update. It appeared that there was no true attempt at downloading as progress steps appeared to happen too quickly in succession - could just be my impression, though. Did a deactivate/reactivate workflow, but nothing changed with respect to the update results. Finally, I did the validate workflow you posted above, but that also did not change the result - no update and no error.

I want to consider that maybe whatever download flag Regions sets for new transactions may not have been set yet? It is possible, but does not seem likely as I have not noticed a delay in the past.

Quicken Kristina

Thank you for your reply,

To continue checking for file-specific issues, please backup your file and deactivate your Regions accounts, then reconnect by navigating to Tools>Add Account and following the prompts. Please make sure to add the problem account as new instead of linking it to the existing account in your file.

Once you add the account as a new account, verify that it can successfully download transactions.

Please let me know how it goes!

rfsinten

Thank you Kristina for continuing to help figure this one out.

In keeping with the sporadic nature of the issue, before attempting your newest test, I attempted an Update Now cycle with the Region accounts and all the accounts updated on the first try. Worked like it is designed. So, I did the same with the BofA accounts, but they did not work – the Visa account continued to pretend it updated without actually updating. So, I decided to attempt your newest test on the BofA accounts – leaving the Regions accounts alone because, “don’t fix it if it is not broken.” From here the explanation gets a little complicated, but I will describe the complete cycle in case there are additional clues from the experience.

Following your sound advice, I first saved a backup. Then, I deactivated all BofA accounts (note: I did not deactivate the associated Merrill Lynch accounts – too many). Went to Tools>Add account and followed prompts. Upon signing in to BofA, it listed all accounts pre-checked for sharing (including the Merrill Lynch accounts). Left them all checked and checked the consent to share data box and waited to be sent back to Quicken, which happened no issue. Quicken interestingly recognized ONLY the Visa account as needing to be added and defaulted to an intended target of a new account (e.g., not linking to an existing account). I took this as a good sign and let that happen. It seemed to work, downloading the last three months of transactions and arriving at a balance consistent with the cleared online balance. Will have to wait to see if future updates now work.

Assuming that future update cycles work, this might be a potential fix, but in using this method, connected history is lost (i.e., transactions further back than 3 months). For a Visa account that carries no intermonth balance, this is not a big deal, but if instead it was an investment account the result would be a loss of continuity within the account, and that loss carries some value. So, I decided to try my own experiment and loaded the backup file and went through the add account workflow, but instead of adding a new account, I linked it to the existing account. This did not work, so I repeated the workflow exactly as you proposed it making the Visa account a new account. This worked as before.

I’m not sure where this leaves us in terms of reliable future updates, but I do want to understand if there is a way to maintain all historical records from the obsolete account in the newly added account. The objective being that there is a single account that contains all historical records and is also updateable going forward. If this can be accomplished in a reasonable fashion (e.g., not moving a million records one-at-a-time from the old account to the new account), then I would consider the problem solved – assuming future updates now work. However, if future updates do not work, AND/OR if I must maintain two accounts to contain both the long-term history and the future transactions, then I would not consider this a viable fix. Does this make sense? – Apologies for the extremely lengthy reply.

[Edited - Readability]