In our DocuSign Demo environment, we noticed that when several envelopes were voided, we did not receive the corresponding connect events. We checked the connect logs and the envelope ID's are not listed. We checked the envelopes in DocuSign and verified that the envelopes were properly voided. We sent a couple more through and recieved the events successfully.
Has anyone else experienced this issue and if so, were you able to correct it?
I'd suggest you verify the following Connect settings via the DocuSign UI (Preferences >> Connect >> [Connect_Configuration_Name]).
Ensure that Allow Envelope Publish is selected:
Ensure that Envelope Voided is selected, and also that All Users Integrated is selected (assuming you want Connect to send notifications for all envelope void events, i.e., for all Envelope Senders)
Provided that the Connect configuration settings are specified as described above (and logs are enabled via the Enable Log checkbox), you should at least see the Envelope Id in the Connect Log file anytime an envelope is Voided (even if some connectivity issue prevented the message from actually reaching your listener). Also, keep in mind that the Log file only preserves the 100 most recent log file entries -- so if there have been more than 100 messages sent since the Envelope Void that you're looking for in the Connect log, it's expected that you wouldn't see that Envelope Id in the log file.
Working with enterprise support, we determined that our missing connect event problem was caused by using the 'Send on Behalf Of' feature. We were listing the authenticating user in the 'Select Users to Integrate', and needed to list the send on behalf of user.
Also, Require Acknowledgement is NOT mentioned here and can and generally does play into debugging connect issues.
Related article:
Docusign Connect retry frequency when require acknowledgement enabled
Related
If an envelope-level (vs account-level) Connect event created via the API with RequireAcknowledgement set to TRUE exhausts all retries, what happens?
In the support article, "Connect Failures and Retries", it mentions, "Administrators can choose to receive email notifications. You receive two proactive emails and another email at deactivation.". However, it seems like that applies to account-level Connect configurations, not envelope-level Connect events created through the API.
Basically, I'm trying to determine what happens after the 15-day mark, when all retries have been exhausted. Ideally, I'd receive an email notification.
After 15 days we will no longer auto-retry events and those specific events will need to be manually retried via the republish tool in the UI or with our new Republish API call.
Envelope-level Connect configurations are not being auto-disabled at this time so there will be no email notification.
We are trying to get a callback from DocuSign to our application when an email failed to be delivered to a signer.
So far, we have set up an ‘AutoResponded’ listener, but did not manage to get a callback.
In our developer account admin settings, we have also enabled following settings:
Account > Updates: Send Individual Messages [Switched status to
Active]
See screenshot
Integrations > Connect: In our custom configuration, under
Trigger Events, we have enabled Recipient Delivery Failed See screenshot
Any advise if we need to enable any other setting? Thanks!
There is a setting which needs to be enabled and it is available only in back-end in DocuSign. You need to create a ticket through our support center provide your account number and ask support to enable it.
You need to be admin on the account to request this change
I am not receiving events for Delete of signers.
Is this an expected behaviour of DocuSign Connect?
These are my steps:
Log in as sender and created the envelope with 4 signers
Click on the email link as the signer and opened the envelope
Signed the envelope as the signer
Log in as sender and deleted one of the remaining 3 signers (This is missing from my Connect event)
I received XML messages for steps 1-3.
However, there was no event trigger for step 4.
I am monitoring this under both Connect Logs and Failures.
I have every event enabled under my Connect Configuration.
Is it expected to not receive an event in this case?
If not, any suggestions on how I can debug why I am not receiving messages?
Just another finding:
An event is triggered for the New Experience.
This behavior is only observed for the Classic Experience.
I believe the behavior you're seeing is by design. i.e., the "Recipient Deleted" action does not correlate to any of the events that can trigger a DocuSign Connect notification. The events that can trigger a DocuSign Connect notification are shown in the Connect configuration UI:
As this screenshot shows, there is no event that correlates to the "Recipient Deleted" action.
If your application needs to know if/when a recipient is removed from an Envelope, you could implement a process that periodically polls in-progress envelopes (List Envelope Recipients) with the goal of detecting if/when a recipient has been deleted. This obviously isn't ideal, as it wouldn't be a real-time notification, but it's likely your only option, given that DocuSign Connect does not currently support notifications for "Recipient Deleted".
UPDATE #1
Interestingly, I've verified the behavior that you've described in your Comment below. I tested the following scenario in both the "New" UI and the "Classic" UI:
Created/sent an Envelope with 2 recipients (sequential routing order: 1, 2)
Immediately thereafter (i.e., while still pending response from the first signer), I corrected the Envelope to delete the second recipient (routing order=2).
Conducting the steps above using the "New" Smartsheet UI triggers a Connect Notification ("Envelope Sent"), while conducting the exact same stepsusing the "Classic" Smartsheet UI does not trigger any notification. This behavior inconsistency seems like a bug to me -- perhaps someone with DocuSign can chime in to confirm/explain.
I have successfully implemented a system that creates documents to be signed via a template using the .NET API, and then has a DocuSign Connect listener that gets called upon the envelope being signed (right now only have Connect reporting on envelope signatures and declines). I have the option set to "Include Documents" on my DocuSign Connect settings. When I create the envelope for signature programmatically with one signer it all works - my Connect listener gets called, the /DocuSignEnvelopeInformation/DocumentPDF/PDFBytes element has Base64 data in it, and I have successfully decoded that and stored it in our doc management system. Cool. Demos well, management loves it.
However, I have noticed at least two scenarios where the /DocuSignEnvelopeInformation/DocumentPDF section isn't being returned at all:
When there are multiple signers.
When the envelope is created manually, even if it uses the same template.
I can still use the Connect response to get the /DocuSignEnvelopeInformation/EnvelopeStatus/DocumentStatuses and extract the document IDs from the DocumentStatus child elements, and then go retrieve those programmatically using the .NET API. But I am wondering why the PDF bytes aren't being consistently returned all the time? Is the above expected behavior? Am I missing something?
I would prefer to save "round trips" and just have Connect deliver all the signed PDFs to me when it calls (and yes, I have read the Recommendations for Receiving Documents section of the DocuSign Connect Guide and understand the trade-offs. Just wondering if I need to code around this issue, or what I am missing?
Hmmm. Envelopes don't get "signed," they get "sent" and "completed." See the envelopeEvents vs the recipientEvents lists in the Connect::Create call.
Currently, there is an existing issue which is that the connect daemon can miss an event if it is quickly superseded by another event. This might be what is happening when you have multiple signers for an envelope. The safest thing to do is to subscribe to all events and then ignore the notifications that are not of interest to you.
The terminal event of an envelope being "completed" will always be sent if you've subscribed to it.
Also, to make your app more bulletproof, I suggest subscribing to the Connect events via the API call (link is above) rather than depending on the human to setup up the subscription correctly. Since an account can easily have more than one connect subscription, you can track which one is your app's by using a specific name for the subscription.
Added
Just now, I created a Connect subscription for just the Envelope Completed event, for all users in my account on demo.docusign.net. As the subscription (listener) url, I used a free account from requestb.in
Using the web user interface (not the API), I created an envelope with two signers. After I completed the envelope, the requestb.in received the notification, it included:
<DocumentPDFs>
<DocumentPDF>
<Name>House architectural overview.pdf</Name>
<PDFBytes>....
as expected. So I'm unable to reproduce your problem. I suggest that you use requestb.in to double-check exactly what is being sent in the notification messages.
I create a pdf on our system and then pass that to docusign for the user to sign. I want to automatically download and save the signed envelopes in our system. Is there a way for docusign to send a post request after the document is signed?
Right now, I randomly (every other hour) connect to docusign and check if the envelope is signed using the docusign api, but this is really not optimal. There are a lot of users who view the pdf in docusign and decide they don't want to sign the document.
The "DocuSign Connect" feature is designed to do exactly that -- send a POST to an endpoint you specify, in real-time, as specified Envelope events occur. Basically it works like this: you build a "listener" app (i.e., a web page that will receive POSTs from Connect), you configure Connect (within your DocuSign account (Preferences >> Connect) to specify the endpoint of your "listener" and select which Envelope events you want your listener to receive notifications for, etc., and once that Connect configuration is enabled, DocuSign will send a POST to your listener endpoint whenever the specified Envelope event(s) occur.
The DocuSign Connect Service Guide (https://10226ec94e53f4ca538f-0035e62ac0d194a46695a3b225d72cc8.ssl.cf2.rackcdn.com/connect-guide.pdf) describes Connect and how to configure/use it -- I'd suggest that you start by reviewing the guide, and post any additional questions here on SO if you run into any issues implementing Connect.