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
Expense - "Waiting for you to pay" message appears for approver after approving report #72524
Version Number: v9.2.30-0 Reproducible in staging?: Yes Reproducible in production?: Yes If this was caught during regression testing, add the test name, ID and link from BrowserStack:#72217 Email or phone of affected tester (no customers):agexptest+pr0810app@gmail.com Issue reported by: Applause Internal Team Device used: Windows 11/ Chrome, Samsung S23FE/ Android 15, iPhone 13 Mini/ iOS 18.5 App Component: Money Requests
Action Performed:
Preconditions:
Have a control workspace with the Rules feature enabled.
Enable the auto approval rule.
Invite an employee and an approver.
Set the approver for everyone's expenses in Workflows.
Submission frequency set to Instantly
Go to staging.new.expensify.com
As the employee, create an expense that exceeds the auto approval amount
Submit the expense
As the approver, open the expense report and approve
Expected Result:
[Approver] The next step message in the header should be "Waiting for Admin to pay expenses."
[Admin] The next step message in the header should be "Waiting for you to pay expenses."
Actual Result:
[Approver] The next step message in the header should be "Waiting for you to pay expenses."
[Admin] The next step message in the header should be "Waiting for Approver to pay expenses."
#72217@nkdengineer@rojiphil@puneetlath This issue was found during testing your PR, can you please check it out and make sure if your PR enabled this behaviour and if its expected or not and we should follow up to fix it? thank you
@puneetlath@rojiphil@NicMendonca 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!
Activity
melvin-bot commentedon Oct 14, 2025
Triggered auto assignment to @NicMendonca (
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.mountiny commentedon Oct 14, 2025
#72217 @nkdengineer @rojiphil @puneetlath This issue was found during testing your PR, can you please check it out and make sure if your PR enabled this behaviour and if its expected or not and we should follow up to fix it? thank you
nkdengineer commentedon Oct 14, 2025
@mountiny It's not related to my PR. My PR only changes the logic related to violation, not next step.
mountiny commentedon Oct 14, 2025
So is this just an exploration issue @jponikarchuk ?
melvin-bot commentedon Oct 17, 2025
@puneetlath, @rojiphil, @NicMendonca Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!
jponikarchuk commentedon Oct 17, 2025
@mountiny This is exploratory issue around PR steps
puneetlath commentedon Oct 17, 2025
I don't understand the bug report. The expected result and actual result are the same.
jponikarchuk commentedon Oct 17, 2025
@puneetlath Not the same
5 remaining items
rayane-d commentedon Oct 28, 2025
My PRs are on staging. @jponikarchuk, could you please check if this issue is still reproducible there?
puneetlath commentedon Oct 28, 2025
Asked for a re-test in Slack.
m-natarajan commentedon Oct 28, 2025
Repro on Web v9.2.39-1 and Repro on iOS v9.2.39-0
ScreenRecording_10-28-2025.11-27-24_1.MP4
bandicam.2025-10-28.11-23-46-703.mp4
melvin-bot commentedon Oct 28, 2025
@puneetlath @rojiphil @NicMendonca 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!
puneetlath commentedon Oct 30, 2025
@rayane-d mind taking a look?
rayane-d commentedon Oct 31, 2025
@puneetlath, This issue was not introduced by my PRs — the problem has existed for a long time. The incorrect logic was first introduced in this PR:
I've created a PR to fix it:
And this one also:
puneetlath commentedon Oct 31, 2025
Ah nice find. Thanks so much for raising the PRs to fix.
rayane-d commentedon Nov 4, 2025
PR is deployed to production. Done.