We are using CV extensively in one of our workflows as the software being automated is very old. The primary CV activity we use is “CV Extract Table”. It has worked for several months and now suddenly, today, the following behavior is seen:
If the screen being OCR’ed has rows of data, the CV Extract Table works just fine.
If the screen being OCR’ed has empty of rows, the CV Extract Able fails with “Element not found”
I’m going to open a ticket but just curious if anyone suddenly has similar experience with CV suddenly breaking ?
This isn’t a condition of whether the object exists or not. It exists. The “CV Extract Table” is wrapped in a “CV Screen Scope”. If the object didn’t exist (which is a frame within a application) the CV Screen Scope would fail first … it does not fail.
Yesterday, this exact same workflow worked just fine when the frame is showing no rows. The CV Extract Table would return a datatable with 0 rows == End of Data. Real Simple. This has worked for MONTHS over thousands of jobs.
Suddenly, today, for no reason, when that same frame is empty (like it should be where there is no data), the CV Extract Table fails.
The only saving grace of error is this ONLY happens when there is no data OR it has successfully OCR’ed and processed what rows were there in the application frame. As rows are processed they no longer show up in the frame. So all rows for all jobs tonight were processed successfully.
No changes of any kind were made to this workflow. This is entirely outside of the workflow and coming from the CV cloud service.
Yeah May be
Any upgrade made with CV Package
Check once with Project dependencies and give a try after upgrading
I hope you would have surround those series of activities with a TRY CATCH block
If not surround that specific CV Extract table activity with a try catch block so that it ensures bot is not getting failed
The content package is noted to be dated. Updating the Content Packs actually breaks the workflows in other ways and work has not yet started to determine why this is.
Yes, the CV Screen Scope and CV Extract Table are both wrapped in their own looped TC Blocks to retry each layer as necessary when each layer fails up to 5 times.
Actually I already a switch activity within my Catch section of the TC Block which deals with specific exception strings is different ways. I can add this “element not found” using it, unfortunately, as an “End Of Data” flag allowing the workflow to continue working normally.
Then deal with figuring out where updating the activity pack break things.
I got confirmation that on 11/9/2021 a change was put into the cloud Computer Vision impacting the “CV Extract Table” activity.
The change was for a bug report (don’t have the specifics). In our case, the change impacted the behavior of the CV Extract Table such that when a frame in the application we use CV Extract Table for has no data showing (and no headers for that matter), the activity now returns a hard exception for “Element not found”.
The “fix” for us was I had to bolt in additional logic ( nothing hard but lots of testing ) into an existing Try Catch block around the CV Screen Scope / CV Extract Table activities such that when the Exception string contains “Element not found” it would setup the necessary “end-of-data” conditions (like creating a datable with headers but has no rows) so that the workflow continues normally and exits gracefully.
and work has not yet started to determine why this is.
) into an existing Try Catch block around the CV Screen Scope / CV Extract Table activities such that when the Exception string contains “Element not found” it would setup the necessary “end-of-data” conditions (like creating a datable with headers but has no rows) so that the workflow continues normally and exits gracefully.