DocuSign not working describes any point in an agreement workflow where an envelope fails to send, reach a signer, open, or complete. Almost every case traces to one of four causes: a service incident, an email delivery problem, an envelope status issue, or a template or integration setting. Working them in that order matters, because the cheapest check sits first.
Why is DocuSign not working on my end?
DocuSign not working traces to those four causes, and the symptom tells you which. For context, US federal law says a signature, contract, or other record may not be denied legal effect, validity, or enforceability solely because it is in electronic form. Start with the DocuSign status center, which lists current incidents and takes seconds, then pause resends until any incident clears so the account avoids duplicate envelopes.
- Signer never receives the email. A spam filter, a wrong address, or embedded signing. Confirm the address, check junk, then resend.
- Envelope shows Failure. An invalid or bounced recipient address. Correct it and resend once.
- Envelope sits in Drafts. The status was never set to sent. Send it from Drafts, or set status to sent in the API call.
- Signing link will not open. An expired envelope, or a browser session for a second account. Use a private window and the original email.
- Fields missing for the signer. Fields assigned to a different recipient. Reassign and resend.
- Template recipient stays blank. Role names differ between the template and the send. Align them and test.
Why did my envelope fail to send?
An envelope fails to send when DocuSign cannot deliver to a recipient address, or when it never left the draft state. The status label separates the two before you change any setting.
Failure points at the recipient address. Confirm the spelling and domain, correct the error, and resend once. Repeated resends to an uncorrected address repeat the same Failure and add noise to the audit trail. Teams copying addresses from a spreadsheet should check for trailing spaces and transposed characters, because both look right on screen. A listing in Drafts means something different: the envelope never went to anyone. Open Agreements, choose Show More, then Drafts, and send from there. Senders who build in batches should check that folder every session, because a draft left behind produces no error at all.
Why is the email not reaching the signer?
Signer emails go missing because of inbox filtering, a wrong address, notification preferences, or embedded signing. Filtering is the likeliest and least visible, since a meaningful share of legitimate email never reaches the inbox at all.
- Filtering. Ask the signer to search junk, quarantine, and Other or Focused folders, then ask IT to review mail gateway logs for that domain. Inbox placement drops to 79.6 percent for hosted business mailboxes, and a corporate signer usually sits behind both a hosting and a filtering layer.
- Recipient preferences. A signer with an account should confirm the envelope-to-sign notification is checked under My Preferences, Notifications, Recipient Notifications.
- Embedded signing and routing. A recipient with a clientUserId is an embedded signer and receives no signing notification at all. Recipients later in a routing sequence get their email only after earlier ones finish. Check both before concluding a message went missing.
An IT allowlist entry for DocuSign notification senders fixes the filtering pattern for every future envelope, which is worth doing once and saves diagnosing it repeatedly.
Why does the signing link fail to open?
A signing link fails when the envelope has expired or been voided, or when the browser holds a session for a different account. Open the original notification in a private browser window, and ask the sender to resend directly if the message arrived through a forward.
A signed-in session for another account conflicts with the recipient address on the envelope, and a private window starts clean. A signer who has an account should log in with the exact address the envelope went to. If that fails, clear cache and cookies, disable extensions, and retry on a second device and a different network, which separates a browser problem from a network restriction in one step. A voided or expired envelope cannot be signed at all, so check the status in the sent folder and issue a new one.
Why are signature fields missing?
Signature fields go missing when they belong to a different recipient, or when the document changed after the sender placed them. Each signature, date, and text field belongs to exactly one recipient, and a field assigned to a second signer or to the sender simply does not appear for the first signer.
The fix is to open the envelope in edit view, confirm the owner of every field on every page, and resend. Swapping a document after placing fields is the other common cause, since the replacement leaves fields out of position or gone. One symptom belongs to the signer alone: the Finish button stays unavailable until every required field is complete, so a signer who cannot submit should scan each page for an incomplete field first.
Why is my template not working?
A template misbehaves when the roles saved in it differ from the roles used at send time. Align the role names first, confirm every field is assigned to a role, and leave roles that change per envelope blank in the template.
- Role names must match exactly. The name in the template and in the send request have to be identical, because a mismatch leaves recipients blank or drops fields silently.
- Reserve fixed recipients. A role saved with a name and email locks to that person, which suits an internal approver who never changes and breaks everything else.
- Send a test envelope. Confirm no signature or text field sits unassigned, then send each template to a test address with every role filled. Template errors surface at send time for the sender and at signing time for the recipient, so open the test from the recipient side, the way CLM testing proves clause and approval logic.
Why does it fail after an API send?
Integration failures trace to three things in order: the envelope status value, the recipient definition, and the account delivery settings. Confirm all three before opening a support case, because support will ask anyway.
- The status value. The default status in a create request is created, which stores a draft. Setting status to sent releases the envelope, and this one line explains a large share of envelopes reported missing.
- The embedded signer flag. The clientUserId property designates embedded signing and suppresses the signing email. Remove it for remote signing, or adopt hybrid signing where the workflow needs both a link and an email.
- Delivery settings and tracing. In Admin, Signing Settings, Envelope Delivery, keep completion emails to embedded signers enabled and suppress disabled, because suppress takes priority. Log the envelope ID with every transaction so a failure traces across systems, and verify completion through a status check or Connect event. Rules mapped without deep condition logic break silently weeks after go-live.
What should you collect before contacting support?
Support resolves a case fastest when the request carries the envelope ID, the exact error text, and the recipient address. Gather seven details and confirm the status center shows no incident before opening the ticket.
- Identifiers and error text. Envelope ID, recipient email address, approximate time of failure, and the exact error message. A screenshot helps where it does not expose contract content.
- Environment and scope. Browser and operating system, the results of the private window and second device tests, and whether the problem hits one envelope or many.
- What stays out. Passwords, OAuth tokens, and private keys never belong in a support request. Documented admin settings shorten this step, since undocumented configuration becomes a liability the moment its author leaves.
A request carrying all seven lets the reviewer trace the transaction without a follow-up question, saving a day.
How do teams prevent these problems before go-live?
Teams prevent most of this by testing every template, role, and integration path before launch, and by naming an owner for admin settings. End-to-end testing in a sandbox environment before any CLM integration goes live keeps these checks out of a support queue.
- Run a test matrix. Push each template through every role combination in a sandbox, record each result, and repeat after any change to a template, role, or mapping.
- Allowlist before launch. Ask IT to allowlist DocuSign notification senders before go-live, so signer emails reach the inbox on day one, ahead of the first complaint.
- Name an owner and staff hypercare. Document the envelope delivery, reminder, and expiration settings, name one person who approves changes, and run a hypercare window catching failed-send patterns.
Conclusion
DocuSign not working becomes diagnosable the moment the cause is sorted into one of four groups: a service incident, an email delivery problem, an envelope status issue, or a template and integration setting. The status center, the envelope label, the recipient address, and the template roles settle most cases in that order, usually in minutes. A test matrix run before go-live prevents most of them reaching anyone at all.
How Basla can help
Basla provides delivery teams for DocuSign implementation, covering legal technology consulting, template and role configuration, integration testing, admin documentation, user acceptance support, and hypercare. The bench includes business analysts and QA specialists who have validated agreement workflows across Onit, DocuSign, and NetDocuments rollouts spanning more than a hundred jurisdictions, including the first-line triage that keeps failed sends away from configuration engineers.
Frequently asked questions
Why is DocuSign not working today?
DocuSign not working today traces to a service incident, an email delivery problem, an envelope status issue, or a template setting. Check the status center first, then the recipient address and the envelope status label.
How do I resend an envelope a signer never received?
Open the envelope, confirm the recipient address, correct any error, and resend. For an envelope already in progress, use Correct so only one stays active and the audit trail holds a single thread.
Why can a signer not see any fields?
The fields are assigned to a different recipient or role. Open the envelope in edit view, reassign each field, check every page, and resend. A document replaced after field placement causes the same symptom.
Why does a template open with blank documents?
Its recipient roles differ from the roles used at send time, or fields are not assigned to a role. Align the role names exactly, assign every field, and send a test envelope opened from the recipient side.
Why did an API send never reach anyone?
The most common cause is a status of created, which stores a draft and releases nothing. The second is a clientUserId on the recipient, which marks them as an embedded signer and suppresses the notification email entirely.
What prevents most of these failures?
A test matrix covering every template and role combination in a sandbox, an IT allowlist for DocuSign notification senders, and one named owner for the delivery, reminder, and expiration settings.
*This article is provided for general information only and does not constitute legal advice. Basla Solutions provides legal technology implementation and support services and does not practice law.*