- The target URL was requested the first time and/or the source has some issues (e.g. invalid SSL certificate, etc.), or the article text / raw text is very long so that the analysis takes longer than 1s.
- Depending on the load of the system the result is in average available within a second. That means with the 2nd request of the same URL you can collect the analysis result. In a real-time environment, it isn’t that critical because you’ll get a full result directly with the 2nd request or over the next few requests.
- Depending on your use case it might make sense to wait a few seconds until the second request is made to get the results. We recommend waiting – if you do a one-time analysis of URLs e.g. like a classification/categorization of URLs – up to 90 seconds before the 2nd request to secure to get a full response.
- If you'll send a huge batch of several millions of different single URLs we recommend to optimize your API request processing. Depending on the number of requests the URLs might be being queued and processed in parallel. The system is scaling instantly but in the nature of the scale processes, this needs some system pre-warm time. In such a case we recommend to wait a couple of minutes before collecting the results.
You can contact us at any time if you need some technical consultancy. Get in touch!