PutConvertWorkbook throws System.Net.WebException: The operation has timed out intermittently

Aspose.Cells Cloud Product Family
1

We are experiencing intermittent timeout exceptions when calling CellsApi.PutConvertWorkbook() to convert an XLSX file to XLSM format. The call fails with a System.Net.WebException: The operation has timed out. originating inside ApiInvoker.GetResponseAsync.

This has occurred multiple times today (2026-07-02) across multiple users with no changes to our code or configuration.

Steps to Reproduce

var request = new PutConvertWorkbookRequest(
    file: workbookStreamToConvert,
    format: "xlsm"
);

var convertedStream = (MemoryStream)cellsApi.PutConvertWorkbook(request);

Stack Trace

System.Net.WebException: The operation has timed out.
   at HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) [HttpWebRequest.cs:1459]
   at TaskFactory<TResult>.FromAsyncCoreLogic(...)
   at WebRequest.GetResponseAsync()
   at ApiInvoker.GetResponseAsync(WebRequest request)
   at ApiInvoker.ReadResponseAsync<T>(WebRequest client)
   at ApiInvoker.InvokeInternalAsync<T>(HttpWebRequest httpWebRequest)
   at ApiInvoker.InvokeApiAsync<T>(HttpWebRequest httpWebRequest)

System.AggregateException: One or more errors occurred.
   at Task.ThrowIfExceptional(bool includeTaskCanceledExceptions)
   at Task<TResult>.GetResultCore(bool waitCompletionNotification)
   at CellsApi.PutConvertWorkbook(PutConvertWorkbookRequest request)
   at Common.ConvertWorkbookToXlsm(File file) [Common.cs:237]

Expected Behaviour

PutConvertWorkbook should successfully convert the workbook and return a stream, or surface a meaningful timeout/retry error with enough detail to diagnose the failure (e.g. which endpoint was called, what the configured timeout is).

Actual Behaviour

The call times out after an indeterminate period, with no indication of which Aspose Cloud endpoint was called or what the server-side status was.

Questions

  1. Is there a known SLA or default timeout configured in ApiInvoker? Can it be overridden?
  2. Is there a recommended retry strategy for transient timeouts?
  3. Was there any service degradation or elevated latency on the Aspose Cells Cloud API on 2026-07-02?
2

@quadrent

We have received your report and are currently investigating the issue. We will update you shortly with our findings.

3

@quadrent

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.

4

This looks like a bot response. This has been an intermittent issue for the last 24hrs in different regions. It has occurred 12 times over the last 24hr and has effected 3 customers.

I was able to replicate the issue locally yesterday twice out of 5 attempts.

5

@quadrent

We have received your report and are currently investigating the issue. We will update you shortly with our findings.

6

@quadrent

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.

7

@quadrent,
Please provide your client_id, and we will look up the call details in the system, analyze them, and provide a satisfactory response. Professionalize.Cells.Cloud is our forum’s AI agent; it constantly checks the questions you raise, performs test analyses, and evolves.

8

@wangtao
Client Id: 8b694b72-6eae-4718-a2bc-2fb12fe8f8a2
Currently we are on Aspose.Cells-Cloud: 24.9.0 on .NET 10

I am in the process of updating to 26.6.4 to see if that mitigates the issue. I am keen to know if you have picked up these failures on your end.

Thanks,

9

@quadrent

We have received your report and are currently investigating the issue. We will update you shortly with our findings.

10

@quadrent

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.

11

@quadrent
Thank you for the information. We will first check and analyze based on your Client ID, and at the same time, do the same test to see if we can reproduce the issue you mentioned.

12

@wangtao
I have retested the new updated version multiple times with no issues.
Le me know if you can trace any failure logs on your end for that client ID.

13

@quadrent

We have received your report and are currently investigating the issue. We will update you shortly with our findings.

14

@quadrent

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.

15

@quadrent,
We reviewed the information you provided and identified a few abnormal records from July 2nd. We also ran a simulation test using Aspose.Cells-Cloud 24.9.0, calling it 10 times consecutively, but were unable to reproduce the issue on our end.

To help us investigate further, could you please provide more details about the spreadsheet file in question? Specifically, we’d like to know:

  • File size
  • Whether it contains images, charts, pivot tables, or other complex elements

Additionally, we suspect that network instability may have contributed to the problem. Our system logs indicate that this type of issue has only appeared in the past few days. We are currently working with other teams to conduct a deeper analysis and will keep you updated on our progress.