Error in Async API in PROD


#1

We are getting error while trying to call Get File in storageAPI

public FileStream GetFile (String userId, String fileId) throws ApiException {
// verify required params are set
if(userId == null || fileId == null ) {
throw new ApiException(400, “missing required params”);
}

This is because in the below newguid and name is coming as null from jobDocumentsResponse and we are passing these parameters in GetFile method. Can somebody please check. Same issue is coming in PROD as well

We did not make any changes in our code and it was working on tuesday.

GetJobDocumentsResponse jobDocumentsResponse = getMergePDFConversionComplete(jobId);
String newguid = jobDocumentsResponse.getResult()
.getInputs()
.get(0)
.getOutputs()
.get(0)
.getGuid();
String name = jobDocumentsResponse.getResult()
.getInputs()
.get(0)
.getOutputs()
.get(0)
.getName();


#2

Hi - this is affecting us in our PROD environment, please advise. Thanks.


#3

Hi @sunil.paul We are sorry to hear that you have such issue. Could you please share with us version of the API and platform that you use.

Thank you.


#4

The issue is because the Group docs merge is taking approx 2.5 minutes (used to merge in seconds before) to merge even a small document. We are using groupdocs-java-client-2.5.1 . Since groupdocs is not merging the document within our configured retry counts, the fileId in the above code is null and this caused the problem. Our UI is getting timed out because of this. Can you please check what is the reason for the sudden degradation of the Services?


#5

Hi @sunil.paul Thank you for this info. I will check it and return to you with the details.

Best regards.


#6

Hi @sunil.paul Sorry but one more question: which App you use , apps.groupdocs.com or dashboard.groupdocs.cloud ?

Best regards.


#7

we are using https://api.groupdocs.com/v2.0


#8

Hi @sunil.paul Thank you, will check.

Best regards.


#9

Please consider it very urgent as it is blocking our PROD env


#10

Hi @pavelteplitsky, let us know if there’s anything else we can provide to help facilitate this. This is a blocker for a very mission-critical part of our application.


#11

Hi @pavelteplitsky - it looks like the processing time is back down to the regular times we expect. Did you change or fix something on your side?


#12

Hi @jwlr I’m glad to hear that all work well for you. We checked our server and found no issues. I will keep you updated if we will found any issues.

Best regards.