Failures with Envelope Writeback and Status Updates (Incident 5505)

Summary

Failures with Envelope Writeback and Status Updates (Incident 5505)

The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Customers may have experienced errors from 2026-07-29 01:43 AM UTC until 2026-07-31 05:14 PM UTC.

• Started

  Jul 31, 2026 · 12:45 PM

• Resolved

  Jul 31, 2026 · 6:01 PM

• Duration

  5h 16m

• Severity

  Minor

• ◐

  Investigating

  Jul 31 · 12:45 PM DocuSign

  Customers in Europe may experience failures with envelope writeback and status update when reviewing Connect logs for DAL envelopes. Engineering teams are engaged and are actively triaging.

• ◐

  Investigating

  Jul 31 · 3:22 PM DocuSign

  We are continuing to investigate this issue.

• ◐

  Investigating

  Jul 31 · 3:23 PM DocuSign

  We continue to investigate the issue and additional resources have been engaged.

• ◐

  Investigating

  Jul 31 · 5:16 PM DocuSign

  We are currently investigating an issue affecting customers using the Salesforce integration across EU and NA regions. Customers may experience failures with envelope write-back and status updates, with the error: "The underlying connection was closed. An unexpected error occurred on send." Services affected: Salesforce connector (envelope write-back, status updates) Impact: Completed envelope statuses may not be reflected in Salesforce. Our engineering teams are actively investigating the root cause across multiple workstreams. We will provide updates as the investigation progresses.

• ◆

  Identified

  Jul 31 · 5:33 PM DocuSign

  We have identified the issue and a fix is being implemented.

• ◆

  Identified

  Jul 31 · 5:51 PM DocuSign

  The issue has been identified and we continue our work to implement a fix.

• ✓

  Resolved

  Jul 31 · 6:01 PM DocuSign

  The incident has been resolved. Incident duration and timelines are subject to revision pending the results of any related investigation. Customers may have experienced errors from 2026-07-29 01:43 AM UTC until 2026-07-31 05:14 PM UTC.