Hi, we are getting the read timeout error while trying to preview the invitation template for V4 mirror links. Below is the request and response we are getting in the debug logs:
Request:
System.HttpRequest[Endpoint=https://api-mirror.aspose.cloud/v4.0/words/merge_cp-451571v5_Digital%20(Live).docx/replaceText?destfilename=merge_cp-451571v5_Digital%20(Live).docx, Method=PUT]
Response:
System.CalloutException: Read timed out
Please check the above issue and let us know if you need more information.
@centris.aspose
You are encountering a read timeout error while calling the Aspose Cloud V4 Mirror API endpoint with a PUT request to replace text in a document . This type of error can occur due to network conditions or server-side processing delays .
To address this issue:
-
Retry Logic: Implement retry logic in your application to handle transient network issues or temporary server delays. Some Aspose SDKs include built-in retry mechanisms, but custom implementations may be needed depending on your environment .
-
Increase Timeout Settings: If possible, adjust the HTTP client timeout settings to allow more time for the operation to complete, especially if the document is large or the server is under load .
-
Check Network Stability: Ensure that the network connection between your application and the Aspose API is stable and has sufficient bandwidth.
If the problem persists, please provide more details or logs for further investigation.
A support engineer will follow up in this thread if needed.
I didn’t find any timeouts on our side, so it’s a Salesforce timeout; we can’t fix it. As soon as the queue feature is available, I will share more details with you.
Thanks for the update. However, we are not seeing the same issue if we switch to v1.1. Are you sure the mirror api is up and running?
We also noticed that the issue is sporadic , the template loads but takes some time the first time , but gives error the second time
Errors :
ASPOSE File Delete Service Exception : DataSourceException:[]: ASPOSE Access Token Exception: Exceeded maximum time allotted for callout (120000 ms)
ASPOSE File Download Service Exception : System.CalloutException: Read timed out
ASPOSE Service Exception: Read timed out (Check network connectivity and Remote Site Settings)
Yes, it is up. We don’t block any connections to our API; only Salesforce has connection issues for some reason.
Could you check on the errors we shared in our earlier post and check if there is some issue from Aspose side for Version 4 Mirror API , as this works for Version 1.1
V1.1 version is deployed in AWS, v4 version is deployed in other infrastructure, so it might be the case.
@yaroslaw.ekimov Can you please have a look at the template we are using and let us know if there is any issue with rendering images while coverting from word to pdf for version 4 of aspose
Pfizer Remote Attendee Invite.docx (837.4 KB)
We are getting below error frequently when trying to preview attached invitation , the file size looks within the limit , please let us know if you find anything
ahm.DataSourceException: ASPOSE Service Exception: Read timed out (Check network connectivity and Remote Site Settings)
What is a file size of the result document? I mean after mailmerge.
@yaroslaw.ekimov The file size after mailmerge is 333.7 KB , ive attached the file here.
Pfizer Remote Attendee Invite-Merged.PDF (333.7 KB)
Below are errors we see for other templates
ASPOSE File Upload Service Exception : DataSourceException:[]: ASPOSE Service Exception: Read timed out (Check file content, size, and network connectivity)
ASPOSE File Delete Service Exception : DataSourceException:[]: ASPOSE Service Exception: Read timed out (Check network connectivity and Remote Site Settings)
Can you please check with team if there is any issue in general from your side for V4 Mirror API , which are reported by others too ?
No, we haven’t got any complaints about API availability. But I brought this to the admin team to address it.
@yaroslaw.ekimov Thanks for the update , also PFA the files before and after mailmerge to check further on this issue , please keep us posted as you get any information
Before :
Pfizer Remote Attendee Invite.docx (837.4 KB)
After :
merge_Pfizer Remote Attendee Invite.docx (324.7 KB)
Thanks for sharing files, I will look into them.
Can we get an update on this as its been 4 days with no update. We cannot migrate our Clients to v4 if its not fully functional and have to keep them on v1 till this is resolved completely.
The admin team didn’t find any issues with neither v4.0 api or api- mirror, they will test the other network options to check if they can reproduce same behavior you observe, and make a fix.
Hi
Did you find any fix or root cause for this?
The admin team found that it is due to a network issue between data centers. They are trying to create another route that won’t be connected to that network. I hope it will be resolved soon.
Could you try using api-mirror now? We’ve moved that service to the other network, so it should be okay now.
We switched to using the mirror API. After making this change, the service executed successfully and no errors were observed. The issue appears to be resolved with this configuration.
Thanks
1 Like
@yaroslaw.ekimov Our clients have switched to Aspose V4 and looks like this is working now.We are able to preview the invitation and testing is in progress , we will let you know if we face any issues , thanks