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
Insights - AI insight cards load infinitely #106591
Version Number: 9.5.36-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from BrowserStack:#106133 Email or phone of affected tester (no customers):osjdonijdsojio@gmail.com Issue reported by: Applause Internal Team Bug source: Exploratory - Significant User Experience Deterioration Device used: Mac 26.5 / Chrome App Component: Other
Action Performed:
Precondition:
Enable insightsAI beta.
Go to staging.new.expensify.com
Go to workspace chat.
Create an expense.
Go to Insights.
Expected Result:
AI insight cards will not appear when not available.
👋 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.
The deploy-blocker investigator identified Improve AI insight cards as the likely cause (medium confidence): it replaced explicit request-completion state with aiInsights === undefined, allowing unavailable insights to display skeletons indefinitely. Keep the deploy blocker and prioritize a compatibility-checked revert; web testing verified expense creation and Insights, but could not confirm beta enablement or reproduce the affected staging state.
Step
Status
insightsAI beta enabledBlocked: no beta control was available, and runtime beta state could not be inspected.
⚠️
Open workspace chatCreated a workspace and opened its expense chat.
✅
Create an expenseCreated a USD 12.34 manual expense; read-back confirmed one expense in a draft report.
✅
Open Insights and observe AI cardsDev NewDot displayed populated Insights without an AI row. This is inconclusive because beta-disabled and unavailable-insight states could not be distinguished; staging reproduction is not claimed.
⚠️
Runtime aiInsights missing versus [] and delayed arrivalThe affected payload was unavailable. Code confirms the regression path: the previous implementation hid absent insights after dashboard completion; the new implementation keeps four skeletons while insights remain undefined, online, and error-free. Explicit [] hides the row, so capturing that value during the failure would challenge this diagnosis. The PR reached staging version 9.5.36-0 approximately 54 minutes before reporting, matching the staging-only symptom. If reverting is unsuitable, model pending, unavailable, and failed states explicitly; do not use chart completion alone because AI results can arrive later. Validate absent data, [], delayed delivery, errors, offline behavior, and filter changes before clearing the blocker.
Activity
applause-bot commentedon Nov 11, 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/6fe0fcbc0a51d1f1cf6c0e2bfc75ebc39bc2522da1fc81ba9433c0bfaa01d780
melvin-bot commentedon Nov 11, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #106133
melvin-bot commentedon Nov 11, 2026
@luacmartins @truph01 you have been assigned to this deploy blocker because you reviewed the offending PR: #106133
melvin-bot commentedon Nov 11, 2026
@mhawryluk you have been assigned to this deploy blocker because you authored the offending PR: #106133
melvin-bot commentedon Nov 11, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Nov 11, 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:
MelvinBot commentedon Nov 11, 2026
🤖 Web test steps verification results:⚠️ partial
The deploy-blocker investigator identified Improve AI insight cards as the likely cause (medium confidence): it replaced explicit request-completion state with
aiInsights === undefined, allowing unavailable insights to display skeletons indefinitely. Keep the deploy blocker and prioritize a compatibility-checked revert; web testing verified expense creation and Insights, but could not confirm beta enablement or reproduce the affected staging state.insightsAI beta enabled
Blocked: no beta control was available, and runtime beta state could not be inspected.Open workspace chat
Created a workspace and opened its expense chat.Create an expense
Created a USD 12.34 manual expense; read-back confirmed one expense in a draft report.Open Insights and observe AI cards
Dev NewDot displayed populated Insights without an AI row. This is inconclusive because beta-disabled and unavailable-insight states could not be distinguished; staging reproduction is not claimed.Runtime aiInsights missing versus [] and delayed arrival
The affected payload was unavailable. Code confirms the regression path: the previous implementation hid absent insights after dashboard completion; the new implementation keeps four skeletons while insights remain undefined, online, and error-free. Explicit [] hides the row, so capturing that value during the failure would challenge this diagnosis. The PR reached staging version 9.5.36-0 approximately 54 minutes before reporting, matching the staging-only symptom. If reverting is unsuitable, model pending, unavailable, and failed states explicitly; do not use chart completion alone because AI results can arrive later. Validate absent data, [], delayed delivery, errors, offline behavior, and filter changes before clearing the blocker.view run · view recording
luacmartins commentedon Nov 11, 2026
NAB this is behind a beta. We're fixing that here https://github.com/Expensify/Web-Expensify/pull/58404