[$500] Request money - Scan - The ongoing receipt scanning process is taking too long (High latency)

@thuyle04

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:

Click on the plus sign and select Request money
Select Scan
Click on the image icon and select any image
Select email recipients and write a simple description
Click the Save button

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

Upwork Job URL: https://www.upwork.com/jobs/~01fe6e5aa6e60b21e0
Upwork Job ID: 1701916951887294464
Last Price Increase: 2023-09-13

Job added to Upwork: https://www.upwork.com/jobs/~01fe6e5aa6e60b21e0

@michaelhaxhiu

Triggered auto assignment to @michaelhaxhiu (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
This bug is not a duplicate report (check E/App issues and #expensify-bugs)
- If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead
This bug is reproducible using the reproduction steps in the OP. S/O
- If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
- If the reproduction steps aren't clear and you determine the correct steps, please update the OP.
This issue is filled out as thoroughly and clearly as possible
- Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.
I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

@jliexpensify

Triggered auto assignment to @jliexpensify (External), see https://stackoverflow.com/c/expensify/questions/8582 for more details.

@mollfpr

Triggered auto assignment to Contributor-plus team member for initial proposal review - @mollfpr (External)

Unassigning myself as I was the 2nd B0 team member assigned.

@mollfpr

Current assignee @mollfpr is eligible for the Internal assigner, not assigning anyone new.

@Gonals

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

How long should it take?

As long as our Smartscan person takes to fill it? There is a guy doing this manually! 😆

@Ngannguyen0308

📣 @Ngannguyen0308! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.

Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

it took quite a long time for the receipt to be scanned

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)

In reality, it's take even more. In this morning i just tested this case (at 9:55AM) but until now (15:30PM), The receipts has not been sent successfully. Here is the image

it took quite a long time for the receipt to be scanned

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)

How is this a bug? The receipt is smartscanning. That takes a while 😕

Am I missing something?

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

Navigation Menu

Repository navigation

[$500] Request money - Scan - The ongoing receipt scanning process is taking too long (High latency) #27328

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Bug0 Triage Checklist (Main S/O)

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[$500] Request money - Scan - The ongoing receipt scanning process is taking too long (High latency) #27328

Description

Action Performed:

Expected Result:

Actual Result:

Workaround:

Platforms:

Activity

melvin-bot commented on Sep 13, 2023

melvin-bot commented on Sep 13, 2023

melvin-bot commented on Sep 13, 2023

Bug0 Triage Checklist (Main S/O)

melvin-bot commented on Sep 13, 2023

melvin-bot commented on Sep 13, 2023

jliexpensify commented on Sep 14, 2023

melvin-bot commented on Sep 14, 2023

mountiny commented on Sep 14, 2023

Gonals commented on Sep 14, 2023

mountiny commented on Sep 14, 2023

Gonals commented on Sep 14, 2023

melvin-bot commented on Sep 15, 2023

Gonals commented on Sep 15, 2023

thuyle04 commented on Sep 15, 2023

thuyle04 commented on Sep 15, 2023

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions