Same is happening with us. In morning as well, I reported that some instances of this on premise approach intermittently started failing. This is very irritating for us and has been raising escalation to get rid of the dependency on aspose. We are seriously considering alternatives as of now as we are helpless in these situations
This is the response from aspose pod for which it is not working:
{
“Name”: “Aspose.Words Cloud API”,
“Version”: “24.12.0”,
“RequestId”: “76aab86e-0d8d-4276-8aa2-07d8cc3db2b7”
}
Issue is under investigation.
I would like to highlight again that this time also, we came to know from clients that they are seeing water mark issues. Please understand that it is most important for us to know this beforehand so that we can switch to other strategy. This is embarrassing for us and has been escalated multiple times
Also, can we get a timeline when it will be resolved?? We need to inform business
I shared that info with the billing team, other product also faced the same issue with billing, they are investigating issue.
It says resolved but we are still seeing watermark!!
Can you please check?
Did you try to restart container to check if it works?
After a while it worked. We kept on trying to restart and after few attempts it started working.
I would like to highlight again that this time also, we came to know from clients that they are seeing water mark issues. Please understand that it is most important for us to know this beforehand so that we can switch to other strategy. This is embarrassing for us and has been escalated multiple times
Please consider this as priority!
I’ll raise this issue with the responsible team.
It is down again. Our business is again impacted. I guess its useless at this point to ask for any support. All we can now try to do is migrate away from aspose: https://status.aspose.cloud/
I’m sorry for the inconvenience. The billing team has been investigating this issue, but the thing is, it seems only you were affected, as we didn’t get any other requests about the trial mode on the Docker image.
Did you get anything on your findings ?
Also, what happened to previous investigation where like we have 3 aspose pods running, but one or two of them, suddenly started giving red marks and /info api response for them was missing additionalInfo array. WHat about this? I already shared the requesteId for that?
As far as I know, the billing team is changing how their service work, but this work is yet to be finished. We are waiting for it to be available in the upcoming release.
We were affected as well: aspose/words-cloud:25.3
Sorry for the inconvenience. I will share that another user faced the same error. Could you share the call info endpoint to check if the license is active?