-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[$250] [HOLD for payment 2024-06-20] Hold expense - Unable to hold expense with failed scanning when there is only one expense #43207
Comments
Triggered auto assignment to @srikarparsi ( |
Triggered auto assignment to @alexpensify ( |
👋 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:
|
@alexpensify FYI I haven't added the External label as I wasn't 100% sure about this issue. Please take a look and add the label if you agree it's a bug and can be handled by external contributors |
We think that this bug might be related to #wave-collect - Release 1 |
I think this is probably related to this PR |
Not reproducible when reverting the PR. The PR adds functionality to hold on single expense views. |
Sorry I'm taking a look now. |
@srikarparsi @blimpich if we reverted the offending PR, do we need to check this off the deploy blocker list: #43168? |
@trjExpensify Yup! Didn't get around to it because I was offline when the revert was merged, but just checked it off. |
Understandable man! |
@alexpensify @srikarparsi re-opened to handle payment for @c3024 |
Noted, I'll work on the payment process before the due date. |
This issue is not caused by my PR #42374 because it even happened in transaction thread report. It has the same root cause with #41655 (comment) which is a BE issue and being worked on. |
Skipping the payment summary for this issue since all the assignees are employees or vendors. If this is incorrect, please manually add the payment summary SO. |
Job added to Upwork: https://www.upwork.com/jobs/~019c2dfe28442e0872 |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @ikevin127 ( |
📣 @c3024 🎉 An offer has been automatically sent to your Upwork account for the Contributor role 🎉 Thanks for contributing to the Expensify app! Offer link |
@c3024 - I've sent over an offer via Upwork. Please accept, and then I can complete the payment process. Thanks! |
Accepted, thanks @alexpensify |
All set, I've completed the payment process in Upwork. Closing! |
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: 1.4.80-3
Reproducible in staging?: y
Reproducible in production?: no new feature
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause internal team
Slack conversation:
Action Performed:
Expected Result:
The held expense with failed scanning will remain held status.
Actual Result:
The held expense with failed scanning return to unheld status.
Workaround:
unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6504168_1717693758278.20240607_010526.mp4
View all open jobs on GitHub
Issue Owner
Current Issue Owner: @alexpensifyUpwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: