Skip to content

Scan - Unable to bulk expense failed scan expense to 0.00 #98788

Closed

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: 9.4.54-2
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #96772
Email or phone of affected tester (no customers): sdsiodjnosdjiodsj@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.5 / Chrome
App Component: Money Requests

Action Performed:

  1. Go to staging.new.expensify.com
  2. Go to workspace chat.
  3. Create a scan expense with invalid receipt.
  4. Wait for scan to fail.
  5. Open the expense.
  6. Select both expenses via checkbox.
  7. Click dropdown button > Edit multiple.
  8. Click Amount.
  9. Enter 0 > Save > Save.
    → The failed scan expense cannot be bulk edited to 0.00.
  10. Open the failed scan expense.
  11. Click Amount.
  12. Enter 0 and save.
    → The failed scan expense can be manually edited to 0.00.

Expected Result:

In Step 9, the failed scan expense can be bulk edited to 0.00.

Actual Result:

In Step 9, the failed scan expense cannot be bulk edited to 0.00. The amount field is still empty after bulk editing to 0.00.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome Safari

Screenshots/Videos

Bug7235689_1786984847746.12.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7235689

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Aug 17, 2026
  2. melvin-bot commented on Aug 17, 2026

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #96772

  3. melvin-bot commented on Aug 17, 2026

    @melvin-bot

    @arosiclair @Ollyws you have been assigned to this deploy blocker because you reviewed the offending PR: #96772

  4. melvin-bot commented on Aug 17, 2026

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  5. m-natarajan commented on Aug 18, 2026

    @m-natarajan

    Not repro, Win 11/Chrome, v9.4.54-4

    Recording.3378.mp4
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.HourlyKSv2ReviewingHas a PR in review

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions