Never before seen error!

Hi Ryan,

Is this error consistent to a certain document or to a certain workflow in your system? Can you share the package ID so I can help you check the package status? And most importantly, do you happen to have this particular PDF or the document that failed to upload to the transaction so we can try to reproduce at our end? Because this "error.eslx.inputValidation.documentPreVerifyInvalidResponseNumberError" usually thrown from the Doc Engine when processing the document. If you didn't change the code recently on your end and the same code works for most of the cases, it's more likely caused by the document itself, in my opinion.

Duo

Duo,

It's good to hear from you! haha

So after some testing I can say this is happening on ever single transaction and it is limited to our account that is associated with the vault. I am wondering if something was changed last night as I sent packages yesterday with success.

Hey Ryan,

Likewise to you! 

From the Trust Center, it doesn't look like there was a release yesterday so I doubt it's because of the product change. Could you pass a sample document that's failing for you (with no Personal Identifiable Information (PII) in it) along with the payload you're sending, so we can see if it's caused by the PDF or package metadata. (If you cannot post them in here, please send to [email protected])

Duo

Duo,

The issue has resolved itself and I am now able to send a package to our sandbox environment. Not sure what the deal was but the same package that was throwing errors is now working. How weird! haha

Thank you for the assistance.