Repository navigation
[Due for payment 2026-10-14] Analyzing is incorrectly shown after creating expense and enabling auto categorizing offline #102604
Description
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.97-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #100248
Email or phone of affected tester (no customers): joinsjdosjodnjsio@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:
Precondition:
- Disable Auto-categorize new expenses in Categories settings.
- Go to staging.new.expensify.com
- Go to workspace chat.
- Go offline.
- Create an expense with Starbucks merchant.
- Go to workspace settings > Categories > Settings.
- Enable Auto-categorize new expenses.
- Open the expense from Step 4.
- Go online.
Expected Result:
In Step 7, after creating expense and enabling Auto-categorize new expenses offline, Analysing will not appear on Category field because expense is already created before Auto-categorize new expenses is enabled.
Actual Result:
In Step 7, after creating expense and enabling Auto-categorize new expenses offline, Analysing is shown on Category field because expense is already created before Auto-categorize new expenses is enabled.
In Step 8, the expense is not categorized despite showing Analyzing.
Workaround:
Unknown
Platforms:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome Safari
Screenshots/Videos
Bug7273073_1790732415190.2.mp4
Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7273073
Issue Owner
Current Issue Owner: @mallenexpensifyMetadata
Metadata
Type
Projects
- Status
Activity
applause-bot commentedon Sep 30, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/d49c5f7c0302c633d180d85946ebcbae5df6469717fe4c415eca8309210a70ec
melvin-bot commentedon Sep 30, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #100248
github-actions commentedon Sep 30, 2026
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
melvin-bot commentedon Sep 30, 2026
@JmillsExpensify @truph01 you have been assigned to this deploy blocker because you reviewed the offending PR: #100248
melvin-bot commentedon Sep 30, 2026
@dukenv0307 you have been assigned to this deploy blocker because you authored the offending PR: #100248
melvin-bot commentedon Sep 30, 2026
💬 A slack conversation has been started in #expensify-open-source
7 remaining items
[-]Analyzing is incorrectly shown after creating expense and enabling auto categorizing offline[/-][+][Due for payment 2026-10-14] Analyzing is incorrectly shown after creating expense and enabling auto categorizing offline[/+]melvin-bot commentedon Oct 7, 2026
@truph01
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.4-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2026-10-14. 🎊
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]
melvin-bot commentedon Oct 7, 2026
@truph01 Still overdue 6 days?! Let's take care of this!
melvin-bot commentedon Oct 9, 2026
@truph01 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!
melvin-bot commentedon Oct 13, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)melvin-bot commentedon Oct 13, 2026
Payment Summary
Resolving PRs:
Analyzing is incorrectly shown after creating expense and enabling auto categorizing offline #102626
Contributor: @dukenv0307 does not require payment (Contractor)
Reviewer: @truph01 owed $175 via NewDot
BugZero Checklist (@mallenexpensify)
truph01 commentedon Oct 14, 2026
This is a follow-up issue, no payment is needed. Closing.