docusign-esign-node-client: Error trying to read form-data of signed document: 444 "The custom error module does not recognize this error"
For the first time, starting about 8:30 am MDT today (Jun 16), using NodeJS package, trying to retrieve form-data from a signed document, I get error: ‘The custom error module does not recognize this error.’ and status: 444, and message: ‘Unsuccessful HTTP response’. See detail below. I opened a ticket with DocuSign support, but I’m not getting any responses.
This is the basically the code I am using. Seems the error is thrown on that last line
const accessToken = await this._getAccessToken(ctx) // Refreshes each hour
let dsApiClient = new docusignESign.ApiClient()
dsApiClient.setBasePath(this.config.baseAccountUri)
dsApiClient.addDefaultHeader('Authorization', 'Bearer ' + accessToken)
let envelopesApi = new docusignESign.EnvelopesApi(dsApiClient)
let results = await envelopesApi.getFormData(this.config.baseAccountId, envelopeId)
The following is the error that comes back
{
"name": "Error",
"stack": "Error: Unsuccessful HTTP response\n at Request.callback (/app/node_modules/superagent/lib/node/index.js:696:15)\n at IncomingMessage.<anonymous> (/app/node_modules/superagent/lib/node/index.js:906:18)\n at IncomingMessage.emit (node:events:539:35)\n at IncomingMessage.emit (node:domain:475:12)\n at endReadableNT (node:internal/streams/readable:1345:12)\n at processTicksAndRejections (node:internal/process/task_queues:83:21)",
"status": 444,
"message": "Unsuccessful HTTP response",
"response": {
"req": {
"url": "https://demo.docusign.net/restapi/v2.1/accounts/723b4584-e964-4391-bb2d-42e6050e477e/envelopes/582420aa-6808-46e0-806c-0fd9aec4f786/form_data",
"data": { },
"method": "GET",
"headers": {
"accept": "application/json",
"node-ver": "v16.15.1",
"user-agent": "node-superagent/3.8.2",
"content-type": "application/json",
"authorization": "Bearer eyJ0eXAiOiJNVCIs...OAgg",
"x-docusign-sdk": "Node"
}
},
"text": "The custom error module does not recognize this error.",
"header": {
"date": "Thu, 16 Jun 2022 16:57:22 GMT",
"connection": "close",
"content-type": "text/html",
"content-length": "54",
"x-docusign-node": "DA1DFE4",
"x-docusign-tracetoken": "c5aab93d-1644-4f84-b745-e5344b11c767",
"strict-transport-security": "max-age=31536000; includeSubDomains"
},
"status": 444
}
Case info…
Case #: 09640094
Account #: 13339722-na4
Subject: Unexpected errors occuring when retrieving form-data from a signed envelope
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 8
- Comments: 22 (3 by maintainers)
We are having the same issue, but with downloading of documents.
We lowered sdk version to 5.7 since in 5.8 the empty body change was introduced.
+1
My organization is also experiencing this novel issue in the last 1-2 days.
I thought support might update this issue - here is the response I got in my ticket a few hours ago …
Steve Docusign, Inc. 06/17/2022
Hello,
Thank you for clarifying this and creating the Github issue for better visibility. This issue appears to be related to some recent security rule enhancements that were implemented on our API. Please be assured that we are actively investigating a solution to this issue and will release a fix as soon as possible. I will provide you with updates on this case as the investigation progresses.
Please let me know if you have any questions in the meantime.
Best regards,
Steve | DocuSign Developer Support
Thanks @brunomilicevic-croatia. @dbbrahmbhatt Can you comment on this line in ApiClient.js? (If I’m reading “git” correctly it looks like it could be from your pull request.) I only use the NodeJS SDK, so I’m limited in my API knowledge. Also, as @Kushagra8888 says, this may only be a misconfigured IIS server issue in the demo servers…
Update: I see this line also in the commit’s CHANGELOG.md …
and the only issue reference to it is here … https://github.com/docusign/docusign-esign-node-client/issues/136 (tagged: DCM-3369) but it appears to me that originally it may only have been the ‘update’ method that needed the empty body. Thoughts?
@dgerbe My original issue is not a problem as of a few mins ago, just checked.
This should be resolved now. Can someone confirm?
Apparently this error is related to IIS which is what must be used by docusign and might be a result of some configuration changes. I suppose this might also happen for other GET calls happening through the SDK. I was able to reproduce the same through Postman by passing an empty object in the body field for a GET request (which is what the SDK also does). However, it will work fine when no body is included.