Skip to content

[Exploratory] Workflow-Approval request displays to the second approver first in the Instantly workspace #105728

Open

Description

@applause-bot

If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.


Version Number: v9.5.28-4
Reproducible in staging?: Yes
Reproducible in production?: Yes
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/81946540/folder/57610718/41236925/1937758742?sort=-identifier
Email or phone of affected tester (no customers): lekima20+60811@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Win 11/Chrome
App Component: Money Requests

Action Performed:

Precondition:

  • User B create a collect workspace
  • User A create a control workspace, setting Submissions: Instantly
  • User A invite user B, user C as employee. Setting default workflow: The first approver: user B, The second approver: user A
  1. Open https://staging.new.expensify.com
  2. User C submit an expense to the user A workspace chat
  3. User C open this report to observe the Next step
  4. User A go to the user C expense detail page
  5. User A approve report
  6. Observe the Next step

Expected Result:

When user C submit expense to the user A workspace chat, user B should receive the approval request as the first approver

Actual Result:

When user C submit expense in user A’s workspace chat, the approval request is displayed to user A. After user A approves the report, approval request is displayed to User B

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7303303_1793681648554.Recording__2669.1.mp4

View all open jobs on GitHub

Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7303303

Issue OwnerCurrent Issue Owner: @situchan

Activity

  1. applause-bot commented on Nov 3, 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/4b4807a9612cfb042e4834b406f83b070eef7ca028a78ff3f7972da2e78fd238

  2. added
    BugSomething is broken. Auto assigns a BugZero manager.
    on Nov 10, 2026
  3. expensify-chore-bot commented on Nov 17, 2026

    @expensify-chore-bot

    this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

  4. m-natarajan commented on Nov 18, 2026

    @m-natarajan

    This issue is failing QA for the PR #106932

    1794991765240.Recording__2719.mp4
  5. situchan commented on Nov 18, 2026

    @situchan
    Contributor

    Checking since I reviewed that PR

  6. self-assigned this
    on Nov 18, 2026
  7. situchan commented on Nov 18, 2026

    @situchan
    Contributor

    I reproduced this bug in production as well so not a regression.
    From the attached video, That report never reached "waiting on bank account".

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

Metadata

Metadata

Assignees

Labels

BugSomething is broken. Auto assigns a BugZero manager.MonthlyKSv2Not a priority

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions