Nuance experienced a minor incident on January 19, 2026 affecting DAX Copilot for Epic - Summary Generation & Delivery, lasting 3h 29m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jan 19, 2026, 08:52 PM UTC
Microsoft is investigating a potential issue affecting summary delivery for some DAX Copilot for Epic customers. More details will be provided when information is available.
- identified Jan 19, 2026, 10:01 PM UTC
Microsoft continues to investigate an issue affecting summary delivery for some DAX Copilot for Epic customers. Please continue to use the application at this time. All summaries are expected to deliver as expected.
- identified Jan 19, 2026, 11:14 PM UTC
Microsoft continues to investigate a service disruption in our US Data Center affecting the timely delivery of summaries for a subset of DAX Copilot for Epic customers. Symptoms may include: • Delayed availability of summaries within Epic • Summaries stuck uploading • Warning message: "You are recording for this patient with DAX Copilot, but you are not in their chart." All summaries are expected to deliver as expected. If you are able to open sidecar and see summary content, but not seeing content in Epic you may apply normal troubleshooting steps of removing and then re-adding the ambient Smart Sections. Additionally, if needed urgently you may also copy/paste from sidecar and place into Epic.
- identified Jan 20, 2026, 12:17 AM UTC
DAX Copilot for Epic delivery services have returned to normal for all new encounters recorded after 6:30 PM Eastern on January 19, 2026. For encounters recorded during the incident window on January19, 2026, most will be automatically reprocessed overnight. However, some encounters may require manual reprocessing by our engineering team. We will share additional updates on the scope and expected timelines for this manual recovery effort in a follow up communication tomorrow morning.
- identified Jan 20, 2026, 12:19 AM UTC
We are continuing to work on a fix for this issue.
- identified Jan 20, 2026, 12:20 AM UTC
We are continuing to work on a fix for this issue.
- identified Jan 20, 2026, 12:21 AM UTC
We are continuing to work on a fix for this issue.
- resolved Jan 20, 2026, 12:22 AM UTC
This incident has been resolved.