-
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
[$500] Request money - Scan - The ongoing receipt scanning process is taking too long (High latency) #27328
Comments
Job added to Upwork: https://www.upwork.com/jobs/~01fe6e5aa6e60b21e0 |
Triggered auto assignment to @michaelhaxhiu ( |
Bug0 Triage Checklist (Main S/O)
|
Triggered auto assignment to @jliexpensify ( |
Triggered auto assignment to Contributor-plus team member for initial proposal review - @mollfpr ( |
Unassigning myself as I was the 2nd B0 team member assigned. |
Current assignee @mollfpr is eligible for the Internal assigner, not assigning anyone new. |
This cannot be external and I think @Gonals already works on some fixes for this |
How is this a bug? The receipt is smartscanning. That takes a while 😕 Am I missing something? |
How long should it take? I guess that is the question :D I will defer to you here, feel free to close |
As long as our Smartscan person takes to fill it? There is a guy doing this manually! 😆 |
📣 @Ngannguyen0308! 📣
|
Yes. The Scan process is not automatic in all cases. For many receipts, an agent has to get to your receipt and manually input the data. It can even take an hour (but it usually takes way less) |
I think it's too soon to have the conclusion that we should close this one, because this feature is not working well at the moment |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Action Performed:
Expected Result:
The result has to happen immediately
Actual Result:
The ongoing receipt scanning process is taking too long
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Version Number: v1.3.69-0
Reproducible in staging?: Y
Reproducible in production?: Y
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
Notes/Photos/Videos: Any additional supporting documentation
574407175230760124.mp4
Screen_Recording_20230913_140140_New.Expensify.mp4
Expensify/Expensify Issue URL:
Issue reported by: @thuyle04
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1693990078757979
View all open jobs on GitHub
Upwork Automation - Do Not Edit
The text was updated successfully, but these errors were encountered: