Skip to content

[Due for payment 2026-08-21] [$250] Workflows - Approval Workflow lags and UI breaks after navigating back #94758

Closed

Description

@applause-bot

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.4.21-2
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/62259274/folder/13176709/41236911/1521896861
Email or phone of affected tester (no customers): applausetester+bm556373@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: android
App Component: Workspace Settings

Action Performed:

Precondition
use Expensifail account

  1. Go to https://staging.new.expensify.com/
  2. Create CONTROL workspace
  3. Go to workflows > click Add approval Workflow > Navigate back

Expected Result:

The Add Approval Workflow button should open the next screen immediately without delay, and when navigating back the Workflows page should retain and display the correct workflow state consistently.

Actual Result:

The Add Approval Workflow button responds with a noticeable delay, and after navigating back the Workflows page displays an inconsistent or incorrect workflow state.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7192514_1782521868596.1.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Mita Rachim
Bug ID: 7192514

Upwork Automation - Do Not Edit
Issue OwnerCurrent Issue Owner: @mallenexpensify

Activity

  1. applause-bot commented on Jun 27, 2026

    @applause-bot
    Author

    While Applause doesn't embed attachments for this bug, here are the links for quick view:
    https://platform.applause.com/services/links/v1/external/dd735f06c7a9a9bbac07ff72ca8a17abcc1b89863ad4922a70fc0eb0146a4413

  2. added
    DeployBlockerCashThis issue or pull request should block deployment
    BugSomething is broken. Auto assigns a BugZero manager.
    on Jun 27, 2026
  3. melvin-bot commented on Jun 27, 2026

    @melvin-bot

    Triggered auto assignment to @roryabraham (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

  4. melvin-bot commented on Jun 27, 2026

    @melvin-bot

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

  5. github-actions commented on Jun 27, 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. added
    ExternalAdded to denote the issue can be worked on by a contributor
    and removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Jun 29, 2026
  7. 100 remaining items

  8. melvin-bot commented on Aug 19, 2026

    @melvin-bot

    @abdulrahuman5196 Huh... This is 4 days overdue. Who can take care of this?

  9. melvin-bot commented on Aug 20, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  10. melvin-bot commented on Aug 20, 2026

    @melvin-bot

    Payment Summary

    Resolving PRs:

    BugZero Checklist (@mallenexpensify)

    • I have confirmed assignees, roles, and Upwork contracts look correct
    • I have paid out Upwork contracts / manual NewDot requests
    • [BugZero Assignee] I have created a GH issue for creating/updating the regression test once above steps have been agreed upon
  11. mallenexpensify commented on Aug 21, 2026

    @mallenexpensify
    Contributor

    @abdulrahuman5196 from the C+ doc

    If there are posts on the PR or issue that reference a regression or deploy blocker, C+ posts on the issue and confirms regression (which will reduce pay by 50%) or provides reasoning why they shouldn’t be considered. If the C+ doesn’t update the issue, the contributor manager making the payment will assume any mention of a regression or deploy blockers reduces the issue amount.

  12. abdulrahuman5196 commented on Aug 23, 2026

    @abdulrahuman5196
    Contributor

    BugZero Checklist:

    • [Contributor] The offending PR and associated issue have been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake.

      Link to the comment on the PR: Not a regression.
      Link to the comment on the Issue: N/a

    • [Contributor] If the regression was CRITICAL (e.g. interrupts a core flow) A discussion in #expensify-open-source has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner.

      Link to discussion: N/A

    • [Contributor] If it was decided to create a regression test for the bug, please propose the regression test steps using the template below to ensure the same bug will not reach production again.

    Regression Test Proposal Template

    Regression Test Proposal

    Precondition:

    • Prerequisites: Use an account with a large number of personal details (to verify performance). Have a workspace with Workflows enabled: go to Workspace > Workflows and enable Approvals.

    Test:

    1. Click "Add approval workflow"
    2. Verify the new route opens with acceptable speed (no noticeable lag or frozen transition)
    3. Type something in the "Find a member" field
    4. Verify the list is filtered properly by the search term
    5. Select and deselect some members and verify the selection updates correctly
    6. Select someone outside the workspace and verify the invitation screen applies

    Do we agree 👍 or 👎

    Zapier Logs Run ID: 00040eee-d736-a4f0-8c94-6934c76c6a54
  13. abdulrahuman5196 commented on Aug 23, 2026

    @abdulrahuman5196
    Contributor

    Hi, No regression from this issue. All linked where wrongly flagged and those issues are already handled by the respective owners.
    @mallenexpensify

  14. mallenexpensify commented on Aug 24, 2026

    @mallenexpensify
    Contributor

    Payment Summary

    Contributor+: @abdulrahuman5196 due $250 via NewDot

    @abdulrahuman5196 thx for commenting on the deploy blockers and providing details.

  15. laurenreidexpensify commented on Aug 31, 2026

    @laurenreidexpensify
    Contributor

    $250 approved @abdulrahuman5196 New Expensify

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

Metadata

Metadata

Labels

Awaiting PaymentAuto-added when associated PR is deployed to productionBugSomething is broken. Auto assigns a BugZero manager.DailyKSv2EngineeringExternalAdded to denote the issue can be worked on by a contributor

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions