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
[Due for payment 2026-10-16] Expense - Error shows up when guest member submits report #103525
Version Number: 9.5.6-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:#97644 Email or phone of affected tester (no customers):jsiojsdonjodsji@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
👋 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.
changed the title [-]Expense - Error shows up when guest member submits report[/-][+][Due for payment 2026-10-16] Expense - Error shows up when guest member submits report[/+]on Oct 9, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.6-6 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-16. 🎊
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]
Activity
applause-bot commentedon Oct 8, 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/66560412d0d97b03fa03434a6ffe394ef68621880d69e92cd22a18e7a11e9e64
melvin-bot commentedon Oct 8, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #97644
melvin-bot commentedon Oct 8, 2026
@JmillsExpensify @flodnv @nkdengineer you have been assigned to this deploy blocker because you reviewed the offending PR: #97644
melvin-bot commentedon Oct 8, 2026
@ShridharGoel you have been assigned to this deploy blocker because you authored the offending PR: #97644
github-actions commentedon Oct 8, 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:
2 remaining items
nkdengineer commentedon Oct 9, 2026
@ShridharGoel Look like it's a backend issue.
m-natarajan commentedon Oct 9, 2026
Issue not repro. (Feature reverted) Windows 11/ Chrome v9.5.6-5
bandicam.2026-10-09.19-47-28-153.2.mp4
[-]Expense - Error shows up when guest member submits report[/-][+][Due for payment 2026-10-16] Expense - Error shows up when guest member submits report[/+]melvin-bot commentedon Oct 9, 2026
@nkdengineer
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.6-6 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-16. 🎊
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 19, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.