Persistent $0 Expense Reports with Empty History

[m-natarajan]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number:
Reproducible in staging?: Needs Reproduction
Reproducible in production?: Needs Reproduction
If this was caught on HybridApp, is this reproducible on New Expensify Standalone?:
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @quinthar
Slack conversation (hyperlinked to channel name): #Quality

Action Performed:

1. Login to ND
2. Observe LHN
3. Open a report with GBR

Expected Result:

All expense reports should have complete history showing:
Creation source (auto-generated vs user-initiated), Any system or user actions taken

Actual Result:

$0 expense reports appear frequently with no clear trigger, Report history section is completely empty

Workaround:

Unknown

Platforms:

Which of our officially supported platforms is this issue occurring on?

• Android: Standalone
• Android: HybridApp
• Android: mWeb Chrome
• iOS: Standalone
• iOS: HybridApp
• iOS: mWeb Safari
• MacOS: Chrome / Safari
• MacOS: Desktop

Screenshots/Videos

Add any screenshot/video evidence

The screenshot and report link is in the OP

View all open jobs on GitHub

[melvin-bot]

Triggered auto assignment to @lydiabarclay (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

[melvin-bot]

Triggered auto assignment to @lakchote (AutoAssignerNewDotQuality)

[MelvinBot]

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

[lakchote]

Daily Update

• I've looked at the logs, focusing on the report ID history 8764193780035003, 30 days from now until today.
  I found something to look at that caught my attention:

Unfortunately, this doesn't seem tied to our root cause.
I've supportal'ed into another account which had this log (applausetester+ck1112@applause.expensifail.com) and the report's total was fine.

• I've asked here to get the results for the transactions associated to the report ID 8764193780035003 along with the report's data
• I tend to think we'd want to do the following to solve the issue from a product's perspective quickly:
  If a report in a processing state has a total equal to $0 (which is invalid since we don't allow submitting expenses for $0 total) -> do not show the report in the LHN.

Next Steps

• @rafecolton to return the results of the queries

ETA

• TBD it should be clearer tomorrow on which way we'd want to solve this

[lakchote]

Daily Update

• Got the results for the transactions associated to that report, turns out there's no transactions.
  The report was created on February which means we don't have access to the complete report's history (we only keep 30 days worth of logs).
• That's why I've asked here @tgolen if he could provide information on the recent report IDs where the issue arose. Hopefully, it'll be recent ones which will help for the reports history.

Next Steps

• Check the results of the report actions associated to the report (asked here)
• Waiting on @tgolen's answer here

ETA

• Still TBD, if the faulty reports appear in the LHN by default a quick frontend fix is doable to mitigate the issue by adding a new condition in reasonForReportToBeInOptionList():

    // Hide reports that have a total of 0, and are in a submitted state
    if (report?.total === 0 &&
        report?.stateNum === CONST.REPORT.STATE_NUM.SUBMITTED &&
        report?.statusNum === CONST.REPORT.STATUS_NUM.SUBMITTED) {
        return null;
    }

In the meantime, a backend investigation would be necessary.