We have received your report and are currently investigating the issue. We will update you shortly with our findings.
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.
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.
We have received your report and are currently investigating the issue. We will update you shortly with our findings.
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.
@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.
@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,
We have received your report and are currently investigating the issue. We will update you shortly with our findings.
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.
@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.
@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.
We have received your report and are currently investigating the issue. We will update you shortly with our findings.
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.
@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.
This error was happening for multiple different files. Files were a maximum of 50KB to 60KB. No images/charts/pivots etc, it does contain a hidden sheet that is used as a lookup for cells on other sheets.
Did your team end up identifying any network instability issues that could have caused this, and if so have these now been resolved?
We have received your report and are currently investigating the issue. We will update you shortly with our findings.
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.
@quadrent ,
Following an investigation with our hosting team, we determined that the timeout errors stemmed from network instability during their recent infrastructure migration. We have been closely monitoring the situation and anticipate that the production cloud cluster migration has been completed. We are currently validating this with the hosting team and will provide a formal confirmation as soon as possible."
1 Like
Thank you for that update.