Computer Vision status stuck on "Running"

Question

question

Daniel-8941 asked May 9, '22 GiftA-MSFT edited May 20, '22

Computer Vision status stuck on "Running"

Hello,

Not sure if this is a temporal problem, but for the past 2 days Computer Vision has been getting stuck on "Running" once in a while. I've left it running to see if it even gives a timeout but gave up after ~5 minutes.

My temporal solution was to run another scan if it gets stuck after 15 seconds (i'm only scanning pdf files with less than 2 pages) and it gives the result after a few seconds, but I'm worried this will eventually give me additional costs since I'm scanning the file twice.

What are my options?

Reusing the code from here, and loop where it gets stuck:

azure-computer-vision

image.png (81.1 KiB)

· 2

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

GiftA-MSFT · May 09 at 09:04 PM

Hi, thanks for reaching out. Can you please share the region of your resource? Thanks.

0 ·

Daniel-8941 GiftA-MSFT · May 09 at 09:09 PM

It's on East US 2

0 ·

Answer 1 · 2022-05-10T15:57:02.64Z

GiftA-MSFT answered May 10, '22 GiftA-MSFT edited May 20, '22

Thanks for the information. I've tried to run the code at several intervals and not able to reproduce this issue. How often do you experience this issue?

· 3

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Daniel-8941 · May 10 at 04:31 PM

It's a bit random, sometimes if happens after 5 executions and sometimes it happens two times in a row. Just tried to replicate it by creating a Computer Vision in Central US and other in West US and haven't had any problems so far. Created two in East US 2 and had the same problem with those.

Sorry, I'm new to Azure and Cloud in general, just created a Log Workspace for the Computer Vision on East US 2 and I'll try to see if there's something I can get from there.

0 ·

Daniel-8941 · May 10 at 05:02 PM

Ok, just edited my code back how it was to see if the process ever finish. Compared to this sunday when I gave up letting it finish, so far it takes 30s, 32s, and 106s, 114s, 115s, 123s to process a file that usually takes 3 seconds. My bad for the wrong assumption, the long time it took when I tested sunday led me to believe they would never finish.

0 ·

GiftA-MSFT Daniel-8941 · May 10 at 07:02 PM

Okay, no worries. I tried in East US 2 and it processed in about 15 seconds on average. Sometimes the duration is shorter or longer than others. I'll be sure to forward this feedback to the product team to see if there's anything that could be impacting the EastUS2 region. Will share updates as soon as I have more information.

0 ·

question