Date and time of most recent update wrong on Dashboard screen

Jack Scripps

Why doesn't the date and time of the most recent update on the Dashboard screen reflect the date of the most recent update? It is always 2 or 3 days behind.

Boatnmaniac

Hmmm….I hadn't noticed that before. I opened one of my test files and noticed that the last update was on 7/12…last Friday. Yet I had run OSU for the file on Sat, Sun and today. I clicked on update and a bunch of transactions for Spending and Investing Accounts downloaded but the last update date still showed 7/12. The data in the dashboard has been updated but that date has not been.

Seems like this might be a bug but maybe someone has some other insight into this that might indicate it is not a bug?

Jack Scripps

Nice to know that the problem is not unique to me…. I think it's a bug.

Boatnmaniac

Yes, I do, too but it does not appear to happen all the time. Today I ran OSU in that same test file, again, yet the last update date still shows 7/12. But in my main data file the last update date after running OSU shows 7/17 (today's date). I don't get it since I know that both files updated properly with new downloads and updated securities prices and online balances so there is something that is not working consistently. I'll be reporting it as a potential bug via Help > Report a Problem. I would encourage you to do the same.

Jack Scripps

Thanks, but I already reported it as a problem….

Quicken Kristina

Hello All,

Thank you for taking the time to visit the Community to report this issue, though we apologize that you are experiencing this.

We have forwarded this issue to the proper channels to have this further investigated. In the meantime, if you haven't already done so, please navigate to Help > Report a problem and submit a problem report with log files attached and (if you are willing) a sanitized copy of your data file in order to contribute to the investigation.

While you will not receive a response through this submission, these reports will help our teams in further investigating the issue. The more problem reports we receive, the better.

We apologize for any inconvenience!

Thank you.    

(CTP-10509)

Boatnmaniac

Thanks, @Quicken Kristina . I reported this issue today. I did not include a sanitized file but I did include a screen shot so the date issue can be seen. And I included the URL to this thread.

maeagle

I have a new problem…last few days my brokerage transactions are downloaded with the previous date and not the correct date. Also my bank downloads show the previous date as the last download. I have the latest version of Quicken. What is going on?

Jack Scripps

Something is definitely screwy. I did a one-step update today, which completed just fine. The date shown as the most recent update on the dashboard screen still shows July 17th. Hmmmm ?????

Boatnmaniac

Yeah, something is not right. For me some files update correctly when OSU is run while for other files the date seems to be frozen in the past.

Jack Scripps

Here's an update — maybe useful, maybe not. I did a one step update this morning (7/25) and all accounts (5 of them) updated just fine. On the dashboard screen, however, the date shown for the most recent update remained at 7/17. As a test, I then chose one of the 5 financial institutions and initiated an update for that institution from it's own transaction register page (using the gear icon at the top right). Again, no problem. The page updated OK (no changes, since I had already updated it using OSU). I then went back to the dashboard page and presto, the date of the most recent update now appears as 7/25. Hmmm …. maybe the date at the top of the dashboard screen is the date of the most recent update that was not initiated using OSU?

Jack Scripps

Referencing my most recent comment, if I am correct in my guess, then I would suggest that the date of the most recent update be removed entirely from the dashboard page, since it is really meaningless…

Quicken Janean

Hi All, Are you still seeing this on the latest R58 release? Please let me know so we can update our team working on this issue. Thanks!

Jack Scripps

Yes, the same problem persists under the latest R58 release. It was updated today to the latest release.