Why a completed DocuSign envelope never reaches Salesforce

How the writeback works

When an envelope completes, DocuSign Connect calls Salesforce. In DocuSign eSignature for Salesforce, the package whose objects start with dfsle, that call does two things. It writes merged values from the signed document back to the record, such as the signed date, and it updates the envelope and recipient status records that your own flows often use to move the deal forward.

If either part throws an error, that part is rolled back and nothing on screen tells you. Two details explain most failures. The writeback runs as the person who sent the envelope, not as an integration user. And the package checks field-level security itself, so even a System Administrator sender can be refused.

Find the error before changing anything

Open the DocuSign log object, dfsle__Log__c, and filter to severity Error around the time the envelope completed. The message names the field, rule or trigger that stopped the update. If your org also has the older package installed (objects starting with dsfs), make sure your flows and reports read the current objects.

The five causes

1. The sender cannot edit a writeback field. The log says the update is unauthorized for named fields. Give every profile or permission set that sends envelopes edit access to every field in the writeback mapping.
2. A validation rule blocks the stage change. Rules that stop reps skipping stages also stop the automation that moves a signed deal forward. The log shows FIELD_CUSTOM_VALIDATION_EXCEPTION. Exempt the signature path, for example with a bypass permission or a condition on the status the writeback sets.
3. A trigger or flow fails downstream. The status update starts your own automation, such as creating billing records or sending notices. If that fails, the update rolls back. The log shows CANNOT_EXECUTE_FLOW_TRIGGER or an Apex stack trace. Fix the automation, then resend the status.
4. A rule rejects a date the flow stamps. Flows that set the close date to today on signature collide with rules that lock the close date after Closed Won. Only stamp the date when it is empty or still open, or exempt the system path.
5. The automation that should run after signature is gone. Nothing errors and nothing happens. This is common after workflow rules and Process Builder were retired without a replacement. Rebuild the step in Flow and backfill the deals it missed.

Repair the deals that were missed

Fixing the cause does not repair the records it already affected. List completed envelopes whose deal is not in the signed state, then resend the status from DocuSign or update the records with a change file you can reverse.

Stop it happening again

Add a daily check that compares completed envelopes with deal status and tells the deal owner when they differ. It takes an afternoon to build and turns a quarter-end surprise into a same-day fix.