Skip to content

[Due for payment 2026-06-23] Workflow - Wrong navigation when returning after inviting new member #78775

Closed

Description

@mitarachim

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!


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.
  1. Go to staging.new.expensify.com
  2. Go to workspace settings > Workflows.
  3. Click Add approval workflow.
  4. Select Owner in Expenses from > Next.
  5. Select User B in Approver.
  6. On confirm page, click Expenses from
  7. Enter User C email > select it > Next.
  8. Click Invite.
  9. Click RHP back button.
  10. 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.

Workaround:

Unknown

Platforms:

  • Android: App
  • Android: mWeb Chrome
  • iOS: App
  • iOS: mWeb Safari
  • iOS: mWeb Chrome
  • Windows: Chrome
  • MacOS: Chrome / Safari

Screenshots/Videos

Bug7040498_1767351637415.2.mp4

View all open jobs on GitHub

Activity

  1. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    DeployBlockerIndicates it should block deploying the API
    on Jan 2, 2026
  2. melvin-bot commented on Jan 2, 2026

    @melvin-bot

    You have been assigned to this deploy blocker because you recently merged this PR: #75589

  3. melvin-bot commented on Jan 2, 2026

    @melvin-bot

    💬 A slack conversation has been started in #expensify-open-source

  4. melvin-bot commented on Jan 2, 2026

    @melvin-bot

    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.

  5. github-actions commented on Jan 2, 2026

    @github-actions
    Contributor

    👋 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:

    1. Identify the pull request that introduced this issue and revert it.
    2. Find someone who can quickly fix the issue.
    3. Fix the issue yourself.
  6. mitarachim commented on Jan 2, 2026

    @mitarachim
    Author

    Issue was found while executing QA for PR #75589

  7. 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
  8. 5 remaining items

  9. nlemma commented on Jun 15, 2026

    @nlemma

    Deploy Blocker #93621 was identified to be related to the PR #80449 that attempted to fix this issue.

  10. lanitochka17 commented on Jun 15, 2026

    @lanitochka17

    Deploy Blocker #93626 was identified to be related to the PR #80449 that attempted to fix this issue.

  11. melvin-bot commented on Jun 15, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  12. lanitochka17 commented on Jun 15, 2026

    @lanitochka17

    Deploy Blocker #93635 was identified to be related to the PR #80449 that attempted to fix this issue.

  13. lanitochka17 commented on Jun 15, 2026

    @lanitochka17

    Deploy Blocker ##93637 was identified to be related to the PR #12343 that attempted to fix this issue.

  14. melvin-bot commented on Jun 15, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  15. melvin-bot commented on Jun 16, 2026

    @melvin-bot

    ⚠️ Looks like this issue was linked to a Deploy Blocker here

    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.

  16. lanitochka17 commented on Jun 16, 2026

    @lanitochka17

    Deploy Blocker #93732 was identified to be related to the PR #80449 that attempted to fix this issue.

  17. 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
  18. melvin-bot commented on Jun 16, 2026

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  19. melvin-bot commented on Jun 16, 2026

    @melvin-bot

    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. 🎊

  20. melvin-bot commented on Jun 16, 2026

    @melvin-bot

    @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]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

BugSomething is broken. Auto assigns a BugZero manager.DailyKSv2Engineering

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions