[Urgent] Words API not responding!

Aspose.Words Cloud Product Family
21

There is still no service for doc to pdf transformation. Can you please check and fix?
Thank you!

22

I am also not able to convert doc to html from last 1 hour, what is the issue please check on urgent basisā€¦

23

The API is working fine now. Sorry for the inconvenience.

24

Hi. Was there another issue yesterday (24th February, around 16:00-17:00 UTC)?

I got a number of errors thrown yesterday in our ā€œinline viewerā€ component. The line of code in question simply creates the API client object:

api = AsposeWordsCloud::WordsApi.new

Error:

**JSON::ParserError** in **inline_viewer#show**
unexpected character: 'Request could not be proxied.

A'

Thereā€™s no mention of any of these outages on the status page

25

image.png (115.8 KB)

Hi I am getting mentioned error, please resolve it ASAP as this is on production environment.

26

I created a task for the admin team to fix this. Iā€™m sorry for the inconvenience.

27

When it will solve??

28

It is fixed. Sorry for the inconvenience.

29

From last 2 to 3 days, continuously errors are comming, and I also not able to add my card for the payment itā€™s decline everytime, for this I need to register again and again for using free api calls. Please guide for add my card for paymentā€¦

30

Please contact sales@aspose.com they will help you with payment.

31

Another issue here yet again @yaroslaw.ekimov

32

I see everything is working now. Sorry for the inconvenience. I asked the responsible team to share why this happened again.

33

@yaroslaw.ekimov
Can you tell what was the issue again so we can communicate to clients?

34

The investigation is ongoing; they restored the serviceā€™s work but are analyzing logs for more information.

35

@yaroslaw.ekimov Can you provide more information regarding the issue as to why it happened

36

I asked the responsible team about an update, and they will share their RCA today.

37

Here is a complete statement from the billing team.
The investigation was concluded, and we determined that a very large number of failed API calls to the /connect/token endpoint was likely the cause of the issue. To mitigate this, we implemented a rate limiter: if a user makes more than 20 failed POST requests to /connect/token within a minute, they will be temporarily blocked from accessing the endpoint for a cooldown period of 10 minutes. When a request is rejected, the system responds with a 429 Too Many Requests status and includes a Retry-After header.

38

Service for converting to pdf do not work since 8:30 UTC. Please fix it !!!

39

I answered to you on other topic.

40

@yaroslaw.ekimov the status page indicates this is down again. Can you please elaborate on the problem, fix, and timeline for this? We are seeing the Aspose Watermark on our documents.

Iā€™ve mentioned this before, but when the service is down, can you consider enabling the licensed service for all Users when your billing is down? This is a seemingly monthly occurrence now.

1 Like