It is not finished yet, so things can change, I’m not sure it make some sense, we will try make it easy to switch between old and new one.
Hi
Did you got any update for us?
Thanks,
I’m testing the plugin, and I hope I can share it with you soon.
Yes, we are almost ready to publish the new plugin. Final tests are ongoing, and then we will publish it.
@yaroslaw.ekimov we are getting a lot of heat and frustration from our Clients. Just now we got another ticket from a Client stating none of the merge is working for them. We would like to get a fix for this immediately to keep our clients happy and not leave us.
I’m sorry you encountered that issue. We can’t solve it, as only your clients experience timeouts. The new version of the plugin we produced is not ready to be published. We are still working on understanding what the reason might be. In the meantime, please copy the entire code you use in all Apex classes. I will try to load it in my org in Salesforce, so maybe that way, I could help you.
@yaroslaw.ekimov These are the classes/code which we are being used for the implementation and shared as per the earlier request.
Please let us know if you still need anything.
Please check that you haven’t uploaded files. Thanks.
Okay, I’m going to use it to test against the latest api, so I will share information after testing.
we were testing and we got below error. Can you check and let us know what is the issue?
DataSourceException: Aspose API HTTP Error 400: Bad Request - Response: {
“errors”: {
“”: [
“Failed to read the request form. Missing content-type boundary.”
]
},
“type”: “RFC 9110 - HTTP Semantics”,
“title”: “One or more validation errors occurred.”,
“status”: 400,
“traceId”: “00-3d2957fe56d60b6eaeb53f9afb7ba93b-7e17cb1c055d298b-01”
}
Sure, I will look into logs.
Please share the client id you use for testing, as for now I can’t find that error.
Last error from that client Id I found at August 8 Found end of mail merge region 'contractDS' without matching start.
I imported the code you shared to the salesforce but couldn’t reproduce that issue yet.
Hi @yaroslaw.ekimov
We also got Read time error for this, want to share this information with you along with logs.
Aspose JWT Request - Endpoint: https://api.aspose.cloud/connect/token
ASPOSE Access Token Exception Details: Read timed out
Read Error.docx (336.7 KB)
Yes, I see that in the logs. Now I’m running tests with the code you shared in Salesforce, trying to reproduce those timeouts
Yes, I was trying to reproduce that error, and it never happened. Also, I looked through our logs and found no requests aborted or failed by timeout. So now I have changed the code you shared, added more logs, and run tests. I hope it will help to understand on which side this error occurs