DocuSign API Not Triggering Void Action and Reminder Emails Still Sending

​@Nambi You can check whether the API call is being triggered by enabling API request logging and then repeating your test to see whether the call appears in the log. 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

Hi ​@Nambi,

What you’re seeing almost always means the envelope is not actually being voided in Docusign, only on the Salesforce side. When an envelope is truly voided in Docusign:

• All outstanding signing activity is cancelled and reminders stop for that envelope.
• By default, recipients get a void/expired notification email (unless your account admin has disabled that specific email type).

Because you’re still getting reminders and not getting a void email, the most likely causes are:

1. Your Salesforce automation is only updating a field in Salesforce (e.g., “Envelope Status = Void”) and not calling the Docusign API to void the envelope.
2. Or the API call to void is being attempted but failing or using the wrong envelopeId, so the real envelope in Docusign remains “Sent/Delivered” and reminders continue.

I’d recommend the following:

• In the Docusign web app, go to Manage.
• Search for the initial contract envelope by Subject or Envelope ID.
• Open the envelope and check:
  • Status – is it “Voided”, or still “Sent/Delivered/Waiting for Others”?
  • History – do you see an entry like “Envelope was voided” (with a void reason)?

If there is no “Voided” event and the status is not Voided, the Docusign envelope has never actually been voided → the API call is not firing or not succeeding. If it is voided and you still get reminders, that would be an edge case, and you should capture the envelope ID, history, and example emails for deeper investigation.

As there is some sensitive information, I recommend creating a support case and sharing the details above (envelope ID, history, and example emails) through it so we can investigate the incident further.

I hope this helps.

Best regards,

Leandro Reis - Developer Support Team