​@tanvirsaad I suggest enabling API request logging and then repeating this test to see whether anything in the request log can help identify the issue. The procedure to enable API request logging is here: https://support.docusign.com/s/document-item?bundleId=jux1643235969954&topicId=poz1578456669909.html.

Here are additional resources about how to use API request logs:

• From the Trenches: How to use API logs
• From the Trenches: Find your REST request using Docusign API logs

Correct me if I am wrong, Creating a envelop with multiple order running ok in my side, and giving api log, but after signing order 1 the status says that the document is sent to order 2 signer, but the mail is not sent, and as this is done by docusign, no log is found about this specific event(sending invitation mail to signer order 2). So was unable to debug this step from my side. I had to “Resend” from my dashboard to send mail to the order 2 signer. 

Hi ​@tanvirsaad,

Please open a case with support providing the envelope ID. This will allow them to check the email logs for failures  

Regards

Ivan D

Hi, guys,

I’m also developing a solution using the Docusign API. Two days ago everything went well, each recipient was receiving mails asking to review and sign a document. Now mails are different, saying much about security, asking if the recipient recognizes the document and its sender and so on. And at the same time this mail goes automatically only to the first recipient, exactly as tanvirsaad described. Every next recipient requires resending the envelope using the Docusign console.

So my conclusion is that it is some new feature (?) of Docusign, with an intention to allow the developer to carefully check the whole process of sending a document to be signed. But if I’m right, it is absolutely necessary to be able to switch this feature off. Especially when the whole solution (using Docusign API) is tested and the tester has no access to the Docusign console.

Is my conclusion right?

Kind regards

Tomasz

​@tml Please see this article for details about the update to the recipient email: https://support.docusign.com/s/document-item?bundleId=yca1573855023892&topicId=odv1749750673856.html.

To explore options for disabling this feature, please open a case with Support and provide your production API account ID.

Hi ​@Julie.Gordon ,

The option of sending, in some situations, a special kind of the email is OK. But I’ve some questions concerning this solution. After the recipient of this mail accepted it and signed the document, it was required to continue the signing process manually, using the Docusign console and the Resend button:

• I’ve observed it on the development environment; does it concern the production environment as well?
• I, as the sender of the envelope, haven’t received any notification saying that I must go to the console and do something with the envelope; this way the signing process stopped waiting to be moved on; is the lack of such a notification on purpose or is the notification missed by accident?
• the envelope and the document are automatically generated by my application based on the same data - on Wednesday, on Friday and today; but only on Friday recipients got these special emails; could it be due to a higher frequency of sending similar envelopes to the same recipient? But this is on the development environment where such a behavior should be treated as nothing special

Regards

Tomasz

Hi ​@tml.

I recommend that you open a support case so that our support team can start an investigation and provide you with answers and a resolution.

Regards.

Julie