Skip to content
Effettua una ricerca per conoscere i prodotti e le soluzioni di InterSystems, le opportunità di carriera e altro ancora.

Alert: Repeated Errors with Modern (New) Interoperability UX Applications Filling Up messages.log

Summary

Alert ID
Product & Versions Affected
Risk Category & Score
Explicit Requirements
DP-453448

- InterSystems IRIS® data platform

- InterSystems IRIS® for Health

- InterSystems Health Connect™

Versions 2026.1, 2026.2

Operational: 4 – High RiskInactivity timeout occurs or the session for an application in the modern interoperability applications exits unexpectedly.

Issue

This issue occurs when a user clicks to open any of the modern (new) interoperability applications (Production Configuration, Rule Editor, DTL Editor, BPL Editor, Message Search/Viewer) and then lets the application become inactive (per the inactivity timeout period for each application). This activity logs-out the user, and the application then loses the context of the namespace. As a result of this, the application incorrectly sends queries to the server without a namespace specified in the URL; because the URL is malformed, when ^%ISCLOG is set to a value of 1 or higher, the request generates one or more entries in the messages.log. Over time, these requests can result in a high volume of error messages.

Impact

When ^%ISCLOG is enabled, the high volume of errors generated in messages.log can impact disk space. It may also generate repeat entries in the audit log and journal files.

If the message logging persists without user intervention (because the session has not been closed), the database may expand significantly enough to undermine system stability and reduce system performance. In some cases, if the logs continue to grow due to the repeated queries, the server may become unresponsive and require a restart.

Resolution

An immediate but temporary resolution on the affected system is to directly disable messages.log entries by setting ^%ISCLOG = 0.

Alternatively, avoid the issue altogether by ending the interoperability session before producing an inactivity timeout. End the session by simply closing the browser tab or navigating away from the modern (a.k.a. new) interoperability applications.

The issue has since been corrected by removing the write to messages.log when the namespace cannot be determined from the URL in the InteropEditors API. This fix is available in versions 2026.1.x onward as noted below in the Maintenance Releases and any more recent version.

  • 2026.1.5 is scheduled for availability on September 30, 2026.
  • 2026.3.0 is scheduled for availability on November 18, 2026.

For More Information

If you have questions or need assistance, please contact the InterSystems Worldwide Response Center (WRC). 

Latest Alerts & Advisories

21 ott 2026
Advisory ID Products Affected Risk Category & Score Explicit Requirements DP-456155 All existing InterSystems interoperability products and solutions that use browser-based XSLT, including:
08 ott 2026
We’re excited to introduce the new InterSystems Software Distribution Platform, available beginning October 8 at downloads.intersystems.com.
11 set 2026
This problem affects all versions of Unified Care Record and Information Exchange prior to 2026.2.
22 lug 2026
The 2026.2 release of InterSystems IRIS® data platform, InterSystems IRIS® for Health™, and HealthShare® Health Connect is now Generally Available (GA). This is a Continuous Delivery (CD) release.
22 lug 2026
This problem affects the following products:
22 lug 2026
This problem affects the following products:
22 lug 2026
This problem affects the following products: