Crash: Mystery Transaction appears in Spending Report, if I click it: "oops something went wrong"

RobWilk

Spending Report:

If I look at "Shopping" as a whole category for the month, this transaction does not appear.

For whatever reason, if I narrow it down to Tuesday through today this week (unclear if that is required), then look at the shopping "subcategory" of shopping (there's not an actual shopping subcategory, it's just uncategorized shopping i guess), a transaction in account "Account" with today's date Category "NA" Amount $0.00 appears in the spending report, if I click it the app crashes.

Coach Jon

Hello @RobWilk,

Thanks for letting us know. This is certainly a strange issue. Can you locate this transaction anywhere else in the web application, like the banking tab? Does this appear in the same report in the mobile application?

Thanks,

Coach Jon

RobWilk

The mobile app spending report doesn't seem to let me drill down to subcategories. So, no it's not there.

This isn't an actual transaction, it's not in an account. [doing a quick look for all transactions dated today in net worth ("all accounts") transactions list —- There is only one transaction dated today and that was my monthly planet fitness dues $25.05 to checking account, which was elsewhere in the report].

So: Agreed - it's strange. No, can't locate. No- mobile doesn't have this feature.

Coach Jon

Hello @RobWilk,

Thanks for the reply! Now that some time has passed, does this transaction still remain in Quicken Simplifi?

Thanks,

Coach Jon

RobWilk

I have -3- of those mystery transactions which (I believe) probably still crash the app:

Coach Jon

Hello @RobWilk,

Thanks for letting us know. I am not sure why these transactions are appearing, though it may be dataset-specific in this case. When did you first notice these mystery transactions appearing? Is there any action you did in Quicken Simplifi where you noticed them afterward?

Thanks,

Coach Jon

RobWilk

May 17th was the first date I noticed them. As i said, all i did is drill down to the shopping subcategory of shopping and they were there. Should i submit logs (does that help fix 'dataset specific' issues?).

Coach Jon

Hello @RobWilk,

Thanks for the reply. Yes, we will need you to submit logs, as this will need to be reported.

1. Log into the Quicken Simplifi Web App.
2.  Select Profile from the left-hand navigation bar.
3.  With the Profile menu open, hold down the Option key for Mac or the Alt key for Windows, and then click Send Feedback.
4.  Leave all boxes checked, add a brief description of the issue, and then click Send.

Thanks,

Coach Jon

RobWilk

Done-

report created - reference id 433780505831307522

-Rob

Coach Jon

Hello @RobWilk,

Thanks for the information. Can you let us know your Browser, its Version, and what Version and Build you are on for Quicken Simplifi?

The Quicken Simplifi Version/Build can be found by scrolling down from the Dashboard page.

Thanks,

Coach Jon

RobWilk

Version: Version: 4.11.0 (25643/29ab392ce)

Browser: At the moment chrome Version 124.0.6367.209 (Official Build) (64-bit) on Windows 11

(Normally I'm on a similar browser on a mac but the problem is happening here too)

Date narrowing not necessasry, it's still showing 3 entries for the very merry month of May

Coach Jon

Hello @RobWilk,

Thanks for the information. We did get this issue reported for you! We will post updates on the issue here when we receive them. One last thing in case we are asked, what do you mean when you stated the program "crashed"? We will want a good understanding just in case.

Thanks,

Coach Jon

Ticket: SIMPL-21195

RobWilk

I got a full screen “oops something went wrong” screen, and it took me away from the report and back to the dashboard like I just signed in.

Coach Jon

Hello @RobWilk,

We are going through old escalations, and I see that the ticket for this issue is still open. Are you still seeing this "oops something went wrong" error issue within Quicken Simplifi? If so, let us know!

-Coach Jon

RobWilk

Haven't seen it in quite a while. Either it was fixed, or I encountered a rarely appearing bug.

-Rob

Coach Jon

Hello @RobWilk,

Thanks for the update, I am glad! We will go ahead and close this ticket in that case. Let us know if you end up seeing this issue again in the future.

-Coach Jon