Words convert API was working fine but now it is suddenly not responding at all. One request with 15kb doc took around 5 minutes for response.
Please check this issue immediately.
curl --location --request PUT 'https://api.aspose.cloud/v4.0/words/convert?format=pdf' \
--header 'Authorization: Bearer token' \
--form 'Document=@"/path/to/doc_template_sample.docx"'
We are seeing this issue too. Second time this month!
We are looking into this issue.
Sorry for the inconvenience.
@yaroslaw.ekimov
we see Aspose words API is working now, can you pls update why we are seeing this issue again? clients are getting frustrated
This time it wasn’t connected to any our work. It was a cluster outage.
We also encountered this issue. This is happening far too frequently and has a significant detrimental impact on our business’ reputation. What is being done to rectify this issue permanently?
Yesterday, there was a cluster issue that we couldn’t predict. Later that night, most of the billing services were migrated to a new cluster, and for now, it seems stable. I asked the admin team about the possibility of new failures, and if migration is completed, they told me that the most challenging part is over, and they put all their efforts into making it as stable as before.
Yes it was the billing service down, they haven’t got the root cause yet, once they shared with me I will update you
I got a RCA from the billing team:
There was a connection issue with the DB, which suddenly stopped responding to requests and sent a timeout exception to the billing application. Our hosting team migrated the VM with the database closer to other applications to avoid network hops. Also, some settings have been updated to address this issue, like increasing the maximum number of connections to DB and keeping alive monitoring has been set to check if the DB is okay.
The issue is happened again.
ASPOSE licencing issue - Free Support Forum - aspose.cloud
Could you please take a look Urgently and let us know what is happening
Status page says it is working fine now, do you still have problems with billing?
it looks like the same connectivity issue.
Could you try to restart your container of aspose to check if it connects to billing to check that you should call v4.0/words/info method
The container restart solved the issu.
Could you please investigate why is this happening ? and what will be the good solution to implement in order nto prevent this happening again
We are now working on changing the request pipeline to avoid such issues.
Thx for you replay.
Please let us know once the solution is in place
Yes I answered you on other topic.
We are currently experiencing a major outage with Aspose. What is going on?? We cannot activate billing on our self-hosted instance or generate your documents on your cloud API.
We need this fixed ASAP @yaroslaw.ekimov
There was a connectivity issue with DB; the billing work has been restored, and the admin team is analyzing why this happened.