未收到AutoResponded事件通知，API Webhook其他收件人事件正常

I’ve run into similar DocuSign Connect event quirks before, so let’s break down why your AutoResponded event isn’t firing for invalid addresses and how to fix this:

1. First, Clarify What the AutoResponded Event Actually Triggers #

The AutoResponded event in DocuSign doesn’t capture all undeliverable email scenarios. It’s specifically designed to trigger when the recipient’s email server sends an auto-reply message (like out-of-office notifications, vacation responders, or automated "I’ll follow up soon" messages).

Hard bounces from completely invalid email addresses (where the domain or user doesn’t exist) fall into a different category—these usually trigger events like Recipient Failed or Envelope Undeliverable, not AutoResponded. That’s why you’re seeing DocuSign send a bounce notification to the sender, but no webhook payload for AutoResponded.

2. Double-Check Your Webhook Configuration #

Even though you mentioned enabling AutoResponded alone for testing, verify these details:

• Log into DocuSign Admin, navigate to your Connect webhook configuration.
• Confirm you’ve selected the correct event name (it might be labeled Recipient AutoResponded or Recipient Auto Response depending on your account version).
• If you want to capture invalid address bounces, add events like Recipient Status Changed (Failed) or Envelope Undeliverable to your webhook’s selected events.

3. Test AutoResponded with a Valid, Auto-Reply Enabled Email #

To confirm your webhook works for the intended AutoResponded scenario:

• Set up an auto-reply (out-of-office) on a valid email address you control.
• Send a test envelope to this address. When DocuSign receives the auto-reply from the recipient’s server, it should trigger the AutoResponded event and send the payload to your webhook URL.
• If this works, your webhook is configured correctly—you just need to adjust which events you’re listening to for bounce scenarios.

4. Check DocuSign’s Envelope Event Logs #

For your invalid address test envelope:

• Open the envelope in DocuSign, go to the History or Event Logs section.
• Look through all recorded events for that envelope. You’ll likely see a Failed status event for the recipient, but no AutoResponded entry. This confirms the event simply isn’t generated for hard bounces.

5. Troubleshoot Webhook Delivery (If AutoResponded Still Doesn’t Fire) #

If even the valid auto-reply scenario doesn’t trigger the webhook:

• Test your webhook URL with a tool like Postman to ensure it accepts POST requests and returns a 200 OK response.
• Check your server/firewall logs to see if DocuSign’s requests are being blocked.
• Check the Failed Requests log in your DocuSign Connect configuration—it will show any errors (like timeouts, invalid SSL, or non-200 responses) that prevented delivery.

内容的提问来源于stack exchange，提问作者Tim H.