You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Chat history is shown and it changes to welcome screen after navigating via header subtitle #105506
Version Number: 9.5.26=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:#100552 Email or phone of affected tester (no customers):osindjodsjsjioj@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Mac 26.5 / Chrome App Component: Chat Report View
Action Performed:
Go to staging.new.expensify.com
Go to Concierge.
Click Hide chat history if welcome screen is not shown.
Open search router.
Type anything.
Click Ask Concierge.
Click on the blue Thread in RHP.
Type anything and send it in the main chat.
Click Concierge on the header subtitle.
Expected Result:
Chat history will remain shown after navigating to Concierge via header subtitle.
Actual Result:
Chat history is shown and then it changes to welcome screen after navigating to Concierge via header subtitle.
👋 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:
Identify the pull request that introduced this issue and revert it.
Root cause: The new Concierge screen shows chat history only while the reportActionID route param is set. It does not save that state anywhere else (useConciergeAskState.ts:60-61). Existing scroll-anchoring code clears that param. When it does, isHistoryCollapsedByUser is still true from step 3, so the welcome screen comes back.
Recommendation: Demote and fix in a follow-up. A revert is too large for this bug. The PR changes about 60 files and depends on a backend change. The bug needs a specific 9-step path, loses no data, and "View chat history" brings the history back. If you want it fixed before deploy, the fix is about 5 lines (below).
How the bug happens
Step 7: The "Thread" link opens the Concierge chat at a linked message, so reportActionID is set and history shows.
Step 9:ParentNavigationSubtitle.tsx:249-259 sets the param again and goes back. The first frame shows history. Then the waiting effect runs, clears the param, and the welcome screen appears.
Other code that clears the param would cause the same flip, for example LinkedActionNotFoundGuard and ReportRouteParamHandler.
When the Concierge chat opens at a linked message, keep history expanded in context state. Add this next to the existing effect in ReportActionsSkeletonGuard.tsx:46-54:
@puneetlath@rushatgabhane@mkhutornyi this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
Activity
applause-bot commentedon Oct 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/f823f59076051a3a1590a901856d1a5b6d318944e5bfea6b4756a1e49948dfec
melvin-bot commentedon Oct 30, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #100552
github-actions commentedon Oct 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 Oct 30, 2026
@puneetlath @mkhutornyi you have been assigned to this deploy blocker because you reviewed the offending PR: #100552
melvin-bot commentedon Oct 30, 2026
@rushatgabhane you have been assigned to this deploy blocker because you authored the offending PR: #100552
melvin-bot commentedon Oct 30, 2026
💬 A slack conversation has been started in #expensify-open-source
MelvinBot commentedon Oct 30, 2026
Deploy Blocker Analysis
Causing PR: [Payment due @mkhutornyi] Add ask Concierge screen. Confidence is high for the PR and medium for the exact timing path. I did not reproduce this in a browser.
Root cause: The new Concierge screen shows chat history only while the
reportActionIDroute param is set. It does not save that state anywhere else (useConciergeAskState.ts:60-61). Existing scroll-anchoring code clears that param. When it does,isHistoryCollapsedByUseris stilltruefrom step 3, so the welcome screen comes back.Recommendation: Demote and fix in a follow-up. A revert is too large for this bug. The PR changes about 60 files and depends on a backend change. The bug needs a specific 9-step path, loses no data, and "View chat history" brings the history back. If you want it fixed before deploy, the fix is about 5 lines (below).
How the bug happens
reportActionIDis set and history shows.useComposerSubmit.ts) makesuseReportActionsNewActionLiveTail.ts:108-127jump to the latest messages. Once that load finishes, it clears the param (lines 176-197). The app then navigates to the new thread, and the Concierge screen freezes underneath it before that effect runs.ParentNavigationSubtitle.tsx:249-259sets the param again and goes back. The first frame shows history. Then the waiting effect runs, clears the param, and the welcome screen appears.Other code that clears the param would cause the same flip, for example
LinkedActionNotFoundGuardandReportRouteParamHandler.None of the other 36 PRs in the Deploy Checklist: New Expensify 2026-10-29 change the Concierge welcome or history state.
Suggested fix
When the Concierge chat opens at a linked message, keep history expanded in context state. Add this next to the existing effect in
ReportActionsSkeletonGuard.tsx:46-54:"Hide chat history" still works, because
collapseHistory()sets the state tofalseand clears the param in one step.Next Steps: Reply with
@MelvinBot implement thisto create a draft PR, or@MelvinBot <your feedback>to refine this analysis.view run
5 remaining items
melvin-bot commentedon Nov 3, 2026
@rushatgabhane Whoops! This issue is 2 days overdue. Let's get this updated quick!
melvin-bot commentedon Nov 3, 2026
@rushatgabhane Whoops! This issue is 2 days overdue. Let's get this updated quick!
melvin-bot commentedon Nov 3, 2026
@rushatgabhane Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
melvin-bot commentedon Nov 5, 2026
@rushatgabhane Huh... This is 4 days overdue. Who can take care of this?
melvin-bot commentedon Nov 5, 2026
@rushatgabhane Huh... This is 4 days overdue. Who can take care of this?
melvin-bot commentedon Nov 5, 2026
@rushatgabhane Eep! 4 days overdue now. Issues have feelings too...
melvin-bot commentedon Nov 6, 2026
@rushatgabhane 6 days overdue. This is scarier than being forced to listen to Vogon poetry!
melvin-bot commentedon Nov 10, 2026
@rushatgabhane 10 days overdue. I'm getting more depressed than Marvin.
melvin-bot commentedon Nov 12, 2026
@rushatgabhane 12 days overdue. Walking. Toward. The. Light...
melvin-bot commentedon Nov 13, 2026
@puneetlath @rushatgabhane @mkhutornyi this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!
expensify-chore-bot commentedon Nov 17, 2026
This issue has not been updated in over 14 days. @puneetlath, @rushatgabhane, @mkhutornyi eroding to Weekly issue.