Originally posted by simonaferrara on September 15, 2026
Hi,
from several days OCR is not correctly detecting zero numbers, and it is replacing zero with O letter.
Eg:
it is detecting
O3:O5:OO AM
instead of
03:05:00 AM
that is the value within the web page.
It is happening also using OCR from the Record Script functionality, and not only by using the Recognize method.
Is anyone else facing this issue?
Originally posted by Patrick_Nagel on September 20, 2026
Did you guys found a solution for this issue?
Originally posted by simonaferrara on September 21, 2026
Patrick_Nagel I’ve opened a ticket to the support, hoping that they will resolve quickly the issue since it is making OCR unusable.
Originally posted by mikel1993 on September 29, 2026
I am still having this issue as well. I have been watching this thread hoping for a resolution
Originally posted by Breanna on September 29, 2026
Same here, this issue has been causing me so much trouble so I keep looking back at this thread for updates. I’ve been running these tests for years without this problem and suddenly it’s happening on all of our automated systems.. I’ve tried so many things to see if it will recognize the pixels correctly, but no luck. I really hope it gets fixed soon. I saw someone opened a support ticket, but wish I could see the status of it.
Originally posted by Breanna on September 29, 2026
Have you seen any updates to the status of the support ticket? I agree that it’s definitely making OCR unusable..
Originally posted by Patrick_Nagel on September 30, 2026
Hi Breanna,
i was so free and opened as well a support ticket this is the response ive got:
"I found a similar issue that our Development team had already been investigating, and they have implemented a fix.
The fix is expected to be included in our next release, which is currently planned for sometime next week."
Originally posted by Breanna on September 30, 2026
Thank you so much for the update! I’m happy to hear that.
