Forum Discussion

LGDTNZ's avatar
LGDTNZ
Occasional Contributor
5 months ago
Solved

An increase in OCR API failures

Hi there, i'm wondering if anyone else has noticed a change in the performance of the OCR API? We run a test suite daily which likely has ~500 OCR API calls. Up until about a month ago, I'd only ...
object recognition
  • LGDTNZ's avatar
    LGDTNZ
    2 months ago

    Thank you everyone for your help. The assistance helped us identify where the issues were occurring. Our infrastructure team were able to setup some monitoring of the OCR API connection and it was down almost 10% of the time. 
    They did some re-routing and we are back to no OCR failures. 

rraghvani's avatar
rraghvani
Icon for Champion Level 3 rankChampion Level 3
5 months ago

That's Swagger, describing RESTful APIs. A UI that renders API documentation based on Swagger/OpenAPI spec file, which users can interact with the API directly from a browser.

If you know what parameters to pass, you can check the Response Headers, for error information, but that's about it.

scot1967's avatar
scot1967
Icon for Champion Level 2 rankChampion Level 2
5 months ago

Right, it's a good troubleshooting step all the same.  You can see the api information, the parameters it expects and even 'Try it out'.  I have used information like this to make calls to APIs from TestComplete that my tested app would normally make and use it to compare the results or verify if the API is even accepting calls or is up at all.  This is very good for intermittent issue where you would like to know more about the failure or exactly what a call is returning. You just call a short function and check what you get as needed and remove it form the test later if you no longer need it.