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
Book travel - User is not redirected to upgrade success page #75038
Version Number: v9.2.57-0 Reproducible in staging?: Yes Reproducible in production?: No If this was caught during regression testing, add the test name, ID and link from BrowserStack:#74035 Email or phone of affected tester (no customers):anythingmo@tstsg.com Issue reported by: Applause Internal Team Device used: macOS/chrome App Component: Other
Action Performed:
Prerequisite:
use a private domain account without a workspace
👋 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.
@isabelastisser@puneetlath This issue can be closed now. The PR #75152 has been in production for two weeks, and since this was a regression, the payment was handled in the original issue #73396.
Activity
melvin-bot commentedon Nov 13, 2025
Triggered auto assignment to @twisterdotcom (
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.melvin-bot commentedon Nov 13, 2025
Triggered auto assignment to @marcochavezf (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Nov 13, 2025
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Nov 13, 2025
👋 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:
marcochavezf commentedon Nov 13, 2025
I don't think it's a backend deploy blocker. Also, I'm going to assign the help label to get more 👀 in case someone knows what could be offending PR
4 remaining items
cristipaval commentedon Nov 13, 2025
this is the offending PR. But I think this is an NAB that can be fixed by the authors and get the regular path deploy.
bernhardoj commentedon Nov 14, 2025
PR is ready
cc: @jayeshmangwani
jayeshmangwani commentedon Dec 8, 2025
@isabelastisser @puneetlath This issue can be closed now. The PR #75152 has been in production for two weeks, and since this was a regression, the payment was handled in the original issue #73396.
puneetlath commentedon Dec 8, 2025
Cool, thanks.