Red flag with no new transactions visible

System

This discussion was created from comments split from:

Fidelity money market automatic redemptions

.

bdantes

https://community.quicken.com/discussion/comment/20536988#Comment_20536988

@BillBarns @Quick92 @Quicken Kristina

I too have seen the "red flag with no transactions" bug for years, with no resolution other than to quit and restart Quicken. I finally reported it as a bug a month or so ago. Not to drift off topic of this thread, but this is just one of less critical but very annoying bugs in Quicken that never get fixed. (Data entry in split transactions and the utility and performance of Find/Replace also come readily to mind.) I wish they'd spend multiple release cycles focusing on bugs and usability / performance issues rather than new features — the tool desperately needs it.

Quicken Kristina

Hello @bdantes,

Thank you for letting us know this has been a recurring issue for you. I moved your post to a new discussion so that I could respond without pulling the other discussion off topic.

The "red flag with no transactions" issue is a known issue, and we do have a Community Alert for it:

https://community.quicken.com/discussion/7960985/ongoing-4-2-25-no-transactions-show-in-compare-to-register-despite-red-flag

If you haven't already done so, I recommend following the troubleshooting from our article on when Quicken says there are transactions to accept but you don't see any:

First, turn automatic entry off or on if it's already off

1. Press Ctrl+A on the keyboard to bring up the Account List, then click the Edit button next to the affected account in the list.

2. In the Account Details window, click on the Online Services tab then click Automatic entry is.

3. Select No on the next dialog box and click OK. Automatic entry should show as "Off" now. If it's already off, select Yes and click OK to turn it on.

4. Click OK to close the Account Details window, then click Done on the Account List.

5. Close Quicken, wait a few seconds, then re-open it. The transactions should appear upon re-opening Quicken.

Then, check the account register and Online Center

Quicken will show you downloaded transactions in multiple locations. The following information shows you how to check for downloaded transactions in the account register and Online Center.

1. Open the account register and select Downloaded Transactions at the bottom of the register.
   • If there are transactions listed, accept them to the register.
   • If there are not any transactions listed, proceed with the next step.
2. Choose the Tools menu > Online Center.
3. Select the appropriate financial institution and account.

4. Select Transactions.

• If transactions are listed, click Compare to Register and accept the transactions. Note: Compare to Register will display online payments on the initial screen. After accepting your online payments, click Continue, Next or Done to see the rest of your downloaded transactions.

• If no transactions are listed or Compare to Register does not allow you to accept the transactions, proceed to the next section.

Lastly, correct data issues

If the Quicken data file is damaged, you might receive prompts about downloaded transactions when you don't have any downloaded transactions.

If you know when this issue began, the best solution is to restore a backup created before this issue began.

If you do not have a backup to restore, Quicken has a built-in utility, Validate, that will correct many data issues. Please note this does not correct all issues and these steps should be taken if the other steps outlined did not resolve the problem.

1. Choose the File menu > Copy or Backup File.
2. Select Create a copy or template, then click Next.
3. Accept all defaults and click Save Copy.
4. Open the New Copy when prompted.
5. Choose File > Validate and Repair File.
6. Select the new copy created in step 3 and click OK.

Note: Depending on the size of your data file, you may need to wait a while for the validation process to finish. Do not use the Task Manager to close Quicken. Quicken displays an error message if it cannot validate the file. If Quicken is able to validate the file and any errors are found, Quicken displays a message, "Data losses were found in your file." You can view the log file for more information.

When the validation process is complete, you will need to Reactivate your accounts for transaction download in the new file copy.

1. Go to Tools > Add Account.
2. Select the bank for the deactivated account(s). If prompted, select the connection method.
3. Enter your credentials and click Connect.
4. When the list of located accounts appears, choose LINK next to each account you want to reactivate.
5. Click Next then Done on the last prompt.
6. After all of your accounts have been Reactivated, complete the Check the account register... section steps above again.

Please let me know how it goes!

bdantes

@Quicken Kristina

Restarting Quicken alone has always made the missing transactions appear in my case. Also, I have validated (and super validated) my data file many times. No issues.

If there is some workaround until this bug is found to get the transactions to show up other than restarting Quicken, that would be good to know. Restarting Quicken is tedious, including having to reenter passwords for the data file itself and the Password Vault.

Quicken Kristina

Thank you for your reply @bdantes,

My apologies for the delayed response. For some reason, I didn't receive a notification that you'd replied.

We do have a Community Alert that you can bookmark in order to receive notification of any updates, when available, and to know when the issue is resolved:

https://community.quicken.com/discussion/7960985/ongoing-4-2-25-no-transactions-show-in-compare-to-register-despite-red-flag

In the meantime, I recommend that you contact Quicken Support about this issue, since there is specific information they need to gather to escalate the issue as needed. The Quicken Support phone number can be found through this link here. Phone support is available from 5:00 am PT to 5:00 pm PT, Monday through Friday.

Thank you!

bdantes

https://community.quicken.com/discussion/comment/20539430#Comment_20539430

@Quicken Kristina

This problem is happening to me fairly often now, and it's very frustrating. I did "Report a Problem" through the software, but honestly all of my direct interactions with phone support have not been good. I really don't want to waste my time there — especially when you pointed out above that it's been a known issue for well over a YEAR! Pretty terrible that has seen no update since then.

Quicken Kristina

Thank you for your reply,

You mentioned that you have validated many times. Did you create a copy of the file and validate the copy? Creating a copy of the file can resolve some issues, since it forces Quicken to rebuild the database. For instructions, see the Lastly, correct data issues section of the article linked below, or review the last section of my initial post.

If creating a copy doesn't correct the issue either, then please provide the following information:

1. When did this issue start? 
   1. You mentioned it's been happening for years, but do you recall a more specific timeframe?
2. How many accounts is this affecting?
3. What types of accounts are affected (checking, savings, 401k, etc)? 
4. When was the last download into the problem accounts?
5. Are there any pending transactions for the accounts on the FI website?

Thank you!

bdantes

https://community.quicken.com/discussion/comment/20541903#Comment_20541903

@Quicken Kristina

Resetting all of the account connections is really agonizing. Also, this process has the same bug as Super Validate (which I've reported a couple of times): it asks to set a new password on the data file, but that password fails to open the file — forcing the Forgot Password process and then Setting the Password again.

The copy did find a PDF attachment that it couldn't copy: "Quicken encountered an error copying a transaction attachment dated <Date> in account '<Account>'. Continue copying attachments?" (to which I said yes) — an error that didn't show up in Validate or Super Validate on the original file. And it left the same dandling / corrupted attachment link in the new file — an attempt to view did nothing, and an attempt to export it crashed Quicken. And an attempt to delete it from the original or copied file does nothing. :-( This account is NOT one of the ones with downloaded transactions.

This flagged downloaded transactions with no actual transactions to show error has been happening repeatedly for as long as I can remember (and I've been using Quicken for literally decades) — but it does seem to have picked up in frequency to several times a month or more. It happens across all types of accounts. I download to all my accounts at least daily.

If your engineers have known of this issue this long, have they ever discovered a consistent reproducer? My presumption is no.

bdantes

@Quicken Kristina Worse than agonizing. After reactivating Fidelity accounts in the new data file, I get CC-601 errors saying there are "We cannot find an account with non-zero balance or with any transaction in the last 12 months. Please check on your Fl website and try again."

Really is frustrating dealing with bug after bug in this software. This stuff should "just work."

Quicken Kristina

Thank you for your replies,

The CC-601 error with Fidelity is a known issue. To receive notification of updates and to know when the issue is resolved, please bookmark this Community Alert:

https://community.quicken.com/discussion/7971667/new-3-2-26-fidelity-investment-fdp-101-cc-601-cp-script-error

To clarify, it sounds like there were other problems, but was the issue with the red flags resolved in the copied file?

Thank you!

bdantes

@Quicken Kristina

The CC-601 errors don’t occur in the original data file. This only happens with the Fidelity accounts for me — everything else when connected in the new file has no issues. Why is only my new file experiencing CC-601 errors with Fidelity?

Regarding the red flags, that issue always goes away after a restart of the app. I won’t know until I’ve seen transactions come down a bunch of times over a month without the issue before I would believe it might be fixed. It’s sporadic. FWIW, I do not believe it’s related to anything corrupted in my data file — I was just trying to do as you asked. I strongly believe this is a software bug, particularly given that it happens to others. Again, have your engineers managed to reproduce this? That’s 99% of the effort to fix most bugs.

Another side note — the fact that data corruption can occur in the first place is sort of amateurish, honestly. Why isn’t Quicken using a bonafide database with ACID to prevent that sort of thing? Having a bunch of hidden features for validating and repairing data does not speak well for the stability of the software. :-( I wish I didn’t have decades of legacy data in Quicken — I would’ve left years ago over all these terrible bugs otherwise.

bdantes

And as long as I’m whining, I find it absurd that Quicken for Mac is STILL not at feature parity with Quicken for Windows, and that migration of data loses information, like attachments. I should be able to use the exact same data file with either product with the exact same functionality. Or at the barest minimum, a truly robust migration tool should exist that loses no data. I’ve had to run a Windows VM for years on my Mac just for Quicken.

Quicken Kristina

Thank you for the follow-up,

CC-601 errors arise in the new file when connecting Fidelity accounts. If these accounts are already linked in your main file, you should only see the issue if you reset or reconnect them.

Again, have your engineers managed to reproduce this?

As far as I know, our teams haven't been able to reproduce the issue. Based on your description, is the problem in your file intermittent?

I strongly believe this is a software bug, particularly given that it happens to others.

To test for a software bug, start by backing up your Quicken file. Next, install a patch that predates the issue's onset. Use the article below to download and apply the appropriate earlier patch: https://www.quicken.com/support/reinstalling-and-patching-your-quicken-subscription-version-after-your-membership-has/#section-windows-3

Thank you!

bdantes

@Quicken Kristina

I guess I haven’t been clear. Yes, the red flag issue is intermittent, sporadic, and unpredictable across many accounts. If it happened every time, I would’ve been able to troubleshoot it with phone support for a fix ages ago. As for rolling back to a previous patch, this problem has been going on for YEARS (and I have used “Report a Problem” multiple times going back years too). And rolling back to a prior patch is a huge risk of (re)introducing more bugs and instability. I don’t think that’s a viable suggestion.

It would even mitigate if there were any workaround other than the severe one of restarting the app. Your engineers should be focused on finding a reproducer — and barring that, introduce extra debug logging around transaction downloads for users to report when the error occurs.

To the CC-601 Fidelity errors I’m now experiencing in the new file only, I did not reset any connections — I simply added them per the instructions. I was beginning to think I needed to deactivate the prior connections in the original file first, but no reconnected accounts besides Fidelity have this CC-601 issue.

So now I’m faced with continuing with my old file or figuring out how to stop these CC-601 Fidelity errors.

(And by the way, I ran into a couple of other bugs when trying to copy and validate the new file, but I won’t go into those here. I’m just getting really exhausted spending hours trying to get the software to do its job without bugs!)

Quicken Kristina

Thank you for your reply,

Since there are other issues in the copied file, I suggest returning to your main file. In the main file, please try following these steps (Warning: Following these steps with your Fidelity accounts may trigger the known issue with CC-601 errors):

1. Create a backup.
2. Go to Add account (+) and add a new "offline account."
3. From the affected account, select all transactions on that account > Right click and select "Move transaction(s)" > From the Move to account dropdown, select the newly added offline account. All transactions should now be in the offline account.
4. Once confirmed that ALL transactions are in the offline account, DELETE the affected account
5. Repeat this process for each affected account.
6. Navigate to Tools>Add Account.
7. Follow the prompts.
8. Carefully link the accounts to the existing nicknames in Quicken.
9. Repeat this process for each financial institution.
10. Monitor to see if the issue is resolved.

If you're willing to help with the investigation of this issue, please navigate to Help>Report a Problem and send a problem report with log files and a sanitized data file attached. If you have a copy of one of the logs from when you validated the file, attaching that would also be helpful. Note: Problem reports allow a maximum of 10 attachments. If you need to send more than 10, you can unselect any file with OLD in the filename, or you can send a 2nd problem report with the additional attachments.

I hope this helps!

bdantes

@Quicken Kristina

At this point, I have both my old (with the two Fidelity connections, which never had the CC-601 errors) and the new (with the new connections that had the CC-601 errors but as of today now don't) files working with everything again. Both files show up completely clean under Super Validation (and I was able to fix the transaction with the corrupted attachment only by completely deleting it and reentering it from scratch — trying to delete the attachment from the existing transaction just did nothing — and btw that transaction went over with them same broken attachment into the new copy, despite a warning saying that the attachment couldn't be copied).

I will wait to see when the Red Flag with no transactions shows again in either file — and try to send log files. I will never be comfortable sending a sanitized data file though, sorry. It's why I use the desktop product only.

Quicken Kristina

Thank you for the follow-up,

Please let me know if the red flag issue happens again.

Thank you!