Great to hear that everything is working fine. Also want to remind that in six months v1.1 version is going to be offline, so you need to consider a transfer from v1.1 to v4.0
Hi Yaroslaw. Thank you for this feedback.
We have been experiencing a problem since this issue was resolved by your team.
We have seen that your API response times have increased significantly since this fix was applied.
These are all taking a long time to execute and resulting in our surrounding processes timing out:
wordsApi.GetDocumentFieldNames
wordsApi.PostDocumentExecuteMailMerge
wordsApi.GetDocumentWithFormat
storageApi.DeleteFile
Please can we urgently get assistance to resolve this?
What version of the API do you use? v1.1 or v4.0?
V1.1 as per the above issue raised previously
I will contact the responsible team to investigate the performance issue.
1 Like
To provide you more details. Pulling API Usage Logs from the Aspose Client portal, we compared two dates 2025/05/09 (before the issues seen in this thread) and 2025/05/28 (current slow performance on Aspose API)
We looked at average duration of the PostDocumentExecuteMailMerge Method on both days. On the 2025/05/09 logs we see an average of 299,45 Duration (we assume this is in milliseconds) for these requests with an average File Size of 62224,98 bytes.
On the 2025/05/28 logs we see an average of 970,47 Duration (we assume this is in milliseconds) for these requests with an average File Size of 62528,59 bytes.
This shows a 3.2 times increase in request duration. The net effect of this is that our processes are timing out resulting in Production failures.
If this data can be used for escalation, it would be highly appreciated.
Please could you check now, v1.1 was rebooted.
Hi Yaroslaw.
We are still seeing performance issues on V1.1. We are still seeing timeouts in our processes. Could you please investigate the degraded performance further?
I shared with them that it didn’t help.
I’ve been told they found the issue and fixed it, please give it a try.
1 Like
Hi Yaroslaw. The fix has been confirmed working by our team. Thank you for resolving.
We will monitor for the next few hours and let you know if anything changes.
Sure, thank you for the feedback