API Methods Throw Exceptions but the Request Appears as 200

@yaroslaw.ekimov Thank you for your fast answer!

Sure, I understand that the billing service is designed to charge only for successful requests, and if there’s a failure, it won’t send a 200 OK response. However, what I’m experiencing is a bit different. When using the api.downloadPresentation method in the SDK, it throws an exception initially, but later the request appears as 200 in the dashboard. It’s puzzling because it happens intermittently, and it’s more likely to occur with larger files.

As for using savePresentation, I notice there are timeouts as well, but eventually, the files do get saved, and the requests are marked as 200. Still using the SDK, it indicates a timeout issue which means my backed reacts accordingly.

Using savePresentation i could begin to check the store periodically if the desired file appears after a timeout… but this is not at all a good solution.

By the way, it happened often yesterday and the day before, I had no of this timeouts today… Maybe some hickups in your services? I will keep you up to date.

still there is the underlying problem that the request is logged as success in your backend…

@yaroslaw.ekimov

I just had it. Request 1-674731da-47473ab2088bd6ec706adca4

http://api.aspose.cloud/v3.0/slides/ce4ec098-b280-4068-8e16-45d9d8cb12c5/split

Error: java.net.SocketTimeoutException: Read timed out

So the call in the SDK timed out after 1 minute. Still the job did run through. I could see the files appear in the storage.

After everything was done, the request returned as successful in the dashboard.

So the problem is just a inconsistancy between the sdk and the real api call. I assume the used OkHttp timeout of one minute is used, but the request still runs.

@a.hellmann,
Thank you for contacting free support. We are sorry that you encountered this problem.

We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): SLIDESCLOUD-2006

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

@a.hellmann,
Our developers have investigated the case. Indeed, the HTTP request timeout in Java SDK is set to 1 minute. So, if a request takes longer, the SDK throws an exception. We will fix it in the nearest release (24.12). We will increase the timeout and make it configurable. But for time-consuming requests, using async cloud API will be a better option. We apologize for any inconvenience caused.

@a.hellmann,
The issues you found earlier (filed as SLIDESCLOUD- 2006) have been fixed in Aspose.Slides Cloud SDKs 24.12.
You can check all fixes on the Release Notes page.