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-06-23] Workflow - Wrong navigation when returning after inviting new member #78775
Version Number: 9.2.91-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:#75589 Email or phone of affected tester (no customers):sjdoinjsdoijsiojdsio@gmail.com Issue reported by: Applause Internal Team Bug source: Pull Request QA execution Device used: Mac 26.1 / Chrome App Component: Workspace Settings
Action Performed:
Precondition:
Admin has invited User B to the workspace.
Go to staging.new.expensify.com
Go to workspace settings > Workflows.
Click Add approval workflow.
Select Owner in Expenses from > Next.
Select User B in Approver.
On confirm page, click Expenses from
Enter User C email > select it > Next.
Click Invite.
Click RHP back button.
Click RHP back button again.
Expected Result:
In Step 8, after inviting user, RHP should return to confirm page or Expenses from page.
Actual Result:
In Step 8, after inviting user, RHP returns to Approver.
In Step 9, RHP returns to Expenses from.
In Step 10. RHP closes.
👋 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 [-]Workflow - Wrong navigation and missing member when returning after inviting new member[/-][+]Workflow - Wrong navigation when returning after inviting new member[/+]on Jan 2, 2026
changed the title [-]Workflow - Wrong navigation when returning after inviting new member[/-][+][Due for payment 2026-06-23] Workflow - Wrong navigation when returning after inviting new member[/+]on Jun 16, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.8-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
@youssef-lr 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]. If no checklist is needed for this issue, you can click: [no checklist button]
Activity
melvin-bot commentedon Jan 2, 2026
You have been assigned to this deploy blocker because you recently merged this PR: #75589
melvin-bot commentedon Jan 2, 2026
💬 A slack conversation has been started in #expensify-open-source
melvin-bot commentedon Jan 2, 2026
Triggered auto assignment to @RachCHopkins (
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.github-actions commentedon Jan 2, 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:
mitarachim commentedon Jan 2, 2026
Issue was found while executing QA for PR #75589
[-]Workflow - Wrong navigation and missing member when returning after inviting new member[/-][+]Workflow - Wrong navigation when returning after inviting new member[/+]5 remaining items
nlemma commentedon Jun 15, 2026
Deploy Blocker #93621 was identified to be related to the PR #80449 that attempted to fix this issue.
lanitochka17 commentedon Jun 15, 2026
Deploy Blocker #93626 was identified to be related to the PR #80449 that attempted to fix this issue.
melvin-bot commentedon Jun 15, 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.
lanitochka17 commentedon Jun 15, 2026
Deploy Blocker #93635 was identified to be related to the PR #80449 that attempted to fix this issue.
lanitochka17 commentedon Jun 15, 2026
Deploy Blocker ##93637 was identified to be related to the PR #12343 that attempted to fix this issue.
melvin-bot commentedon Jun 15, 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.
melvin-bot commentedon Jun 16, 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.
lanitochka17 commentedon Jun 16, 2026
Deploy Blocker #93732 was identified to be related to the PR #80449 that attempted to fix this issue.
[-]Workflow - Wrong navigation when returning after inviting new member[/-][+][Due for payment 2026-06-23] Workflow - Wrong navigation when returning after inviting new member[/+]melvin-bot commentedon Jun 16, 2026
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Jun 16, 2026
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.4.8-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-06-23. 🎊
melvin-bot commentedon Jun 16, 2026
@youssef-lr 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]. If no checklist is needed for this issue, you can click: [no checklist button]