Solventum incident

Integrated session launch failures affecting web-to-web (wcintf) integrations following application of 25.5.20.n release

Major Resolved View vendor source →

Solventum experienced a major incident on July 3, 2025 affecting PRODUCTION (A) - 360 Encompass and PRODUCTION (A) - 360 Encompass and 1 more component, lasting 13d 6h. The incident has been resolved; the full update timeline is below.

Started
Jul 03, 2025, 02:10 PM UTC
Resolved
Jul 16, 2025, 08:47 PM UTC
Duration
13d 6h
Detected by Pingoru
Jul 03, 2025, 02:10 PM UTC

Affected components

PRODUCTION (A) - 360 EncompassPRODUCTION (A) - 360 EncompassPRODUCTION (A) - 360 EncompassNon-production (A) - 360 EncompassNon-production (A) - 360 EncompassNon-production (A) - 360 EncompassNon-production (A) - 360 EncompassPRODUCTION (A) - 360 EncompassPRODUCTION - Coding in the cloud (CITC)PRODUCTION - Coding in the cloud (CITC)

Update timeline

  1. investigating Jul 03, 2025, 02:10 PM UTC

    The 25.5.20.n release of 360 Encompass includes changes to CRS/Codefinder that may cause certain types of integrated session launches to fail. Support and development teams are investigating root cause and developing workarounds. This incident will be updated when RCA is finalized and a general remediation is developed.

  2. identified Jul 03, 2025, 02:31 PM UTC

    The issue affects web-to-web/wcintf integrations (such as those created by Meditech and WellSky) and causes the integrated session to fail at launch: the launching application will appear to "hang" while attempting to launch the integrated session. The issue does not affect integrated sessions created using the older WinAppLink/weblink.exe method, such as those created by Epic. Development teams are designing a fix presently.

  3. monitoring Jul 03, 2025, 04:36 PM UTC

    Development teams are producing a public KB for this issue and have begun to work directly with sites to resolve their issues ahead of the official KB release. With the direct support of developers, some affected sites have been completely recovered and are functioning normally. General guidance for resolving this issue is expected shortly.

  4. resolved Jul 16, 2025, 08:47 PM UTC

    This incident has been resolved.