Blank pages with OCREngine=3 take ~63s and return E101 timeout instead of a quick empty OCR result

OCR.space Free OCR API
, , , ,
1

Hi OCR.space team,

I’m seeing a reproducible issue with blank/empty pages when using OCREngine=3.

Tested endpoints:

  • free endpoint
  • pro1 endpoint
  • pro2 endpoint

Parameters:

  • OCREngine=3
  • language=auto
  • scale=true
  • isTable=true
  • detectOrientation=true

Input:

  • blank white PNG, 1200x800

Observed behavior:
The API waits about 63 seconds, then returns HTTP 200 with:

OCRExitCode: 6
IsErroredOnProcessing: true
ErrorMessage: [“E101: Timed out waiting for results”]
ParsedResults:

Expected behavior:
A blank page should return quickly with a successful empty OCR result, e.g. empty ParsedText / no detected lines.

For comparison, the same blank image with OCREngine=2 returns quickly with an empty ParsedText result.

Could you confirm whether this is expected behavior for OCREngine=3? From an API consumer perspective, blank pages are common in scanned PDFs, and waiting ~63 seconds per blank page makes batch processing difficult.

Thanks!

2

Issue confirmed.

From an API consumer perspective, blank pages are common in scanned PDFs, and waiting ~63 seconds per blank page makes batch processing difficult.

Totally agree! This issue is on our todo list. Thank you for reporting it.

3

That’s good to know. Looking forward to a resolution on this.

I also really appreciate the replies here. One of the reasons we decided to try OCR.space was seeing how consistently you respond to support issues on this forum. It gives us confidence that we can build on top of your service.

Thanks!

4

This issue is fixed with the new OCR Engine3 update. - If you see other or new issues, please let us know.