We’re investigating repeated timeouts when calling CellsApi.PutConvertWorkbook to convert a generated Excel workbook to XLSM.
The affected attempts occurred on 21 September 2026, between approximately 00:18 and 00:30 UTC. Three attempts for the same workbook failed, with the surrounding processing step taking approximately 102 seconds per attempt.
Our environment:
NuGet package: Aspose.Cells-Cloud26.6.4
Runtime: .NET 10.0.7
OS: Ubuntu 24.04.4
Application hosting region: AWS ap-southeast-2
The call is:
var request = new PutConvertWorkbookRequest(localPath, "xlsm");
var convertedStream = (MemoryStream)cellsApi.PutConvertWorkbook(request);
The exception is a System.AggregateException containing:
System.Net.WebException: The operation has timed out.
The inner stack includes HttpWebRequest.EndGetResponse, ApiInvoker.GetResponseAsync, ReadResponseAsync, InvokeInternalAsync and InvokeApiAsync.
The workbook is loaded and populated using IronXL, then serialised with workbook.ToBinary() and written to a temporary .xlsm file before the Aspose call. We are still verifying whether those input bytes are XLSX or already XLSM.
An earlier, different workbook completed the same generation/conversion step in approximately five seconds.
Could you please confirm:
Were there any Cells Cloud incidents or degraded performance during that UTC window?
Is there a default request timeout near 100 seconds in this SDK, and how should it be configured?
Could submitting an already-valid XLSM workbook for conversion to XLSM cause this behaviour?
What request identifiers or diagnostic logging would help you investigate?
We can arrange a sanitised sample workbook if needed.
After testing, the API you mentioned is working correctly. Could you please provide more details about your environment and usage scenario? We will continue to investigate and update you if we find any issues.
I have provided all the information I have available. We continue to get the same error across all our environments making our SaaS product un usable. Please escalate
@Professionalize.Cells.Cloud please escalate this issue, we are receiving intermittent outages from this endpoint. This same issue has shown up back in July during a migration on your side.
@quadrent Hello, we have conducted tests from multiple locations and found that while some areas are experiencing timeouts, others are functioning normally, and some are encountering issues. Could you please let us know which region you are in? This will help us analyze the network conditions.
We are also coordinating with the server team to address this issue.
If the parameters meet your requirements, please let me know which programming language you are using, and I will provide the corresponding sample code.