Hi, I’m using the ‘Read PDF with OCR’ activity in Community Edition, but I’m encountering an error.
Read PDF With OCR: Request CorrelationId: 645bd8e7-73e9-4627-871d-9c2de9d13d55
Request PredictionId:
Error performing OCR: Server response: Invalid API key specified Error:UiPathOCRInvalidApiKey CF-RAY: cid-v1:354c7cb9-ae5a-4d16-84a7-f13242bbac6d. AppId:
Thanks in advance.
Hi @jai_kumar2
I think Community edition doesn’t provide official API keys for cloud OCR services ,
you’ll need to use free/local OCR engines like Tesseract instead.
Happy automation
Which OCR engine you are using?
Hi @ashokkarale iam using UiPath document ocr engine.
Hi @prashant1603765 Tesseract is also throwing error.
Can you share a screenshot of your OCR activity with properties ?
For UiPath OCR you will need valid API Key, which is not available for community version.
If this is for testing, maybe you can just mock the read PDF part to get to the next part?
If you give the file to a GPT it can extract the text for you I think and you can just read it from a text file or something?
Both the activities are throwing API error
Digitize document activity - properties
Read PDF with OCR Properties
@jai_kumar2 check the properties of OCR as well.
As I said, why not just mock this out for whatever training or testing you are doing.
If you want to do this for real you can buy the licence?
Hi @Jon_Smith Thanks for your input, but I’d like to clarify my concern.
Your suggestion is not helping to the community. you suggested mocking things out or purchasing the license — but what’s the point in insisting on buying a license when the issue seems to stem from the Community Edition itself? The lag or error is reproducible, and that indicates it’s something that should ideally be fixed by the platform, not bypassed by pushing users toward a paid version.
From a developer’s point of view, if the Community Edition is being promoted for learning and testing, stability should still be a priority. Suggesting a license as a workaround doesn’t actually solve the root cause — in fact, it shifts attention away from addressing a genuine performance or bug issue in Studio.
I believe it’s important to raise such issues, especially if they affect workflow or learning. If the intention is to move more users to licensed versions, that’s understandable — but bugs and lags shouldn’t be dismissed or left unfixed in the free version either.
I don’t agree.
The OCR stuff requires a licence, so it won’t work on Community, nor should we expect it to or try to make it so.
It does work on Enterprise licences, so to completely an evaluation or training you can skip this step and do a simple mock exercise.
I don’t see the issue here. Everything doesnt need to work on community, and stability is not the key feature there, infact the opposite, its where new stuff is refined before it goes to the stable version.
Perhaps explain why mocking won’t work for you in this situation and we can suggest other things that you find more constructive?
