Skip to content

Workflow - Clicking Next with a limit set but no approver does not return to workflow editor #79154

Closed

Description

@lanitochka17

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.96-1
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: #78350
Email or phone of affected tester (no customers): applausetester+bm1021@applause.expensifail.com
Issue reported by: Applause Internal Team
Bug source: Pull Request QA execution
Device used: Web, mweb, android
App Component: User Settings

Action Performed:

  1. Go to https://staging.new.expensify.com/
  2. Create a workspace and add members
  3. Go to Workspace > Workflows
  4. Click to create a new approval workflow
  5. Add members to "Expenses from"
  6. Select an approver
  7. Enter a report amount (e.g., $500)
  8. Leave the additional approver empty
  9. Click Next

Expected Result:

According to the PR steps, it should return to the workflow editor without a limit config set

Actual Result:

Clicking Next with a limit set but no approver does not return to the workflow editor; instead, it throws an error.

Workaround:

Unknown

Platforms:

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

Screenshots/Videos

Bug7043956_1767902164008.bandicam_2026-01-08_22-55-29-358.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.
    on Jan 8, 2026
  2. melvin-bot commented on Jan 8, 2026

    @melvin-bot

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

  3. melvin-bot commented on Jan 8, 2026

    @melvin-bot

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

  4. melvin-bot commented on Jan 8, 2026

    @melvin-bot

    Triggered auto assignment to @joekaufmanexpensify (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 8, 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. abzokhattab commented on Jan 8, 2026

    @abzokhattab
    Contributor

    This is the expected result per the issue description #75775

    cc @JS00001 @arosiclair

  7. removed
    DeployBlockerCashThis issue or pull request should block deployment
    on Jan 9, 2026
  8. JS00001 commented on Jan 9, 2026

    @JS00001
    Contributor

    This is expected

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

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions