Back to Docusign.com
The DocuSign User Interface in the Agreements view is able to show whether an email has a Delivery Failure. This is under the Sent status / category. However, since there is a delivery failure that recipient has not received the envelope, therefore the envelope is really NOT sent in the business sense. Today, the business thinks that everything OK when it is clearly NOT OK. And we do NOT want to rely on a report.
The DocuSign Connect callback JSON shows the happy envelopeSummary.status =
"envelopeSummary": {
"status": "sent",
This does not follow the traditional ‘lookout below’ pattern, where at the highest level the payload indicates there is a problem with the envelope, and if you want more details, you must dig deeper into the payload.
And yes! There is detail below. In the JSON Connect payload it states there is a problem inside one of the recipients.signers object:
"status": "autoresponded",
"autoRespondedReason": "smtp; 550 5.4.1 Recipient address rejected: Access denied.\n [LN2PEPF000100CD.GBRP265.PROD.OUTLOOK.COM 2025-02-05T11:17:05.398Z\n 08DD3E4205AB062F]",
The DocuSign platform knows how to catch this issue and has mapped this as Delivery Failure in the UI layer.
Therefore, the envelopeSummary.status IDEALLY would be mapped to ‘Delivery Failure’ or a more general ‘Error’ status, and our code would catch this, and then navigate to the next level down to the recipients.signers[*].status to test each recipient’s status. Plus, we have to test every type of recipient. Ouch.
We general do NOT like to look at the lowest level first as that is not performant. I am sure the DocuSign UI would like this too.
