We are having issue when we try to mail merge documents which have a large data payload.
Up until this week it was working fine, then since last night in particular (first issue noted at 1140 PM BST 13/8/24), we now cannot successfully compile a document using the API unless it has low amounts of data in the request. This is a major breaking issue as most of our request have imagery and so a large payload (when compared to just a request with plain text data).
This what we are seeing, alot of 504 gateway timeouts and before the default threshold set of 300s.
Below is a screenshot. Timings are in Indian Standard time (GMT + 5:30)
image_2024-08-14_144723611.jpg (311.8 KB)
Update
- we have been retrying every 5 mins or so with a request to see if your back end becomes operational again. We have had one success circa 12:25pm BST in approx 50 attempts. It has now reverted to bad gateway again.
Please look into this urgently.
Hi @bedarley111111 !
Please provide the template document, mail merge data, and the request parameters you are using. This will help us reproduce the issue and resolve it.
@bedarley111111
1 more thing - can you please provide full response from our server? Include http headers?
Hello @Ivanov_John You system came back up yesterday at around the time when you guys start your day. so circa 2pm BST
Can I ask how aspose runs itas dev ops / change management as we seem to be blighted by regular issues which when you evaluate the timeline or support responses suggest you roll out bad code/ have poor provisioning/ scaling.
Is it possible to have advanced notice of changes being made?
@bedarley111111
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): WORDSCLOUD-2818
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
The issues you have found earlier (filed as WORDSCLOUD-2818) have been fixed in this update. This message was posted using Bugs notification tool by Ivanov_John