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 2025-11-17] [$250] Tack distance-Upgrade add rate expense, recipient add as Admin briefly display and disappear #73483
Version Number: v9.2.38-1 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from BrowserStack:https://test-management.browserstack.com/projects/2219752/test-runs/TR-1469/folder/18717689/49855697/972471661 Email or phone of affected tester (no customers): N/A Issue reported by: Applause Internal Team Device used: Win 11/Chrome App Component: Money Requests
Action Performed:
Precondition: Login with Expensifail account and the user does not have workspace
👋 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.
When creating a distance expense with a recipient who doesn't have a workspace, the CreateWorkspace API receives recipient data in the memberData field but completely ignores it, causing recipients to disappear from the workspace.
Root Cause
The CreateWorkspace API receives the correct payload with recipient information in memberData but returns an incorrect response that excludes the recipient from the workspace.
The api is not returning correct data. it only returns the current workspace owner.
Proposed Solution
The CreateWorkspace API should be fixed to return the correct response that includes the recipient in the employeeList when the payload contains valid memberData.
Implementation
The `CreateWorkspace` API will update to handle `employeeList` list correctly.
I got a PR up for review. This was a frontend problem and could have been fixed externally @dominictb. You mentioned there was a problem with OpenWorkspaceMembersPage not returning the proper data, but if a read command is returning the wrong data then usually there's a problem with a preceding write command, as was the case here.
changed the title [-][$250] Tack distance-Upgrade add rate expense, recipient add as Admin briefly display and disappear[/-][+][Due for payment 2025-11-17] [$250] Tack distance-Upgrade add rate expense, recipient add as Admin briefly display and disappear[/+]on Nov 10, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.47-1 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@neil-marcellini@sakluger The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero 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]
Activity
melvin-bot commentedon Oct 25, 2025
Triggered auto assignment to @sakluger (
Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.melvin-bot commentedon Oct 25, 2025
Triggered auto assignment to @marcaaron (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Oct 25, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Oct 25, 2025
👋 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:
abbasifaizan70 commentedon Oct 25, 2025
Bug: CreateWorkspace API Ignores memberData Field
Summary
When creating a distance expense with a recipient who doesn't have a workspace, the
CreateWorkspaceAPI receives recipient data in thememberDatafield but completely ignores it, causing recipients to disappear from the workspace.Root Cause
The
CreateWorkspaceAPI receives the correct payload with recipient information inmemberDatabut returns an incorrect response that excludes the recipient from the workspace.API Payload
API Response
The api is not returning correct data. it only returns the current workspace owner.
Proposed Solution
The
CreateWorkspaceAPI should be fixed to return the correct response that includes the recipient in theemployeeListwhen the payload contains validmemberData.Implementation
Files Affected
CreateWorkspaceAPI implementationmelvin-bot commentedon Oct 27, 2025
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.
37 remaining items
neil-marcellini commentedon Nov 6, 2025
I got a PR up for review. This was a frontend problem and could have been fixed externally @dominictb. You mentioned there was a problem with OpenWorkspaceMembersPage not returning the proper data, but if a read command is returning the wrong data then usually there's a problem with a preceding write command, as was the case here.
[-][$250] Tack distance-Upgrade add rate expense, recipient add as Admin briefly display and disappear[/-][+][Due for payment 2025-11-17] [$250] Tack distance-Upgrade add rate expense, recipient add as Admin briefly display and disappear[/+]melvin-bot commentedon Nov 10, 2025
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Nov 10, 2025
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.47-1 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 2025-11-17. 🎊
melvin-bot commentedon Nov 10, 2025
@neil-marcellini @sakluger The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero 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]
sakluger commentedon Nov 17, 2025
No payment is required since this was handled internally.