Skip to content
Sök för att lära dig mer om InterSystems produkter och lösningar, karriärmöjligheter med mera.

Advisory: Purge Task for Expire and Query Edge Gateways Fails to Complete Due to Streamlet Matcher Errors

This problem affects the following products:

  • All versions of HealthShare Unified Care Record®

Requirements:

  • Expire and Query Edge Gateway

HealthShare Edge Gateways support several cache types, one of which is “Expire and Query.” An Expire and Query Edge Gateway includes a CacheExpirationTimeout that marks data as out-of-date after a certain period of time, for example, one hour. Data that is marked as expired is deleted on a regular basis by the ExpireQueryPurgeTask. The tasks loops through the MRNs on the Edge and deletes those marked as expired. In certain environments, the Expire and Query Edge Gateway purge task may fail to complete due to errors encountered while deleting data from the table HS_SDA3_Streamlet.Matcher.

When this occurs, the task stops processing remaining records, leaving obsolete entries unpurged and allowing the Edge Gateway storage to grow uncontrollably, which can eventually affect system performance and stability. Keeping data that should be purged also presents potential privacy issues.

You may see the following error:


Error occurring during DELETE in table 'HS_SDA3_Streamlet.Matcher':
$ZE=<SUBSCRIPT>%SQLDelete...

This error is typically triggered by malformed or abnormally large index values stored under the MatcherI global. While these entries can be created normally, they later become inaccessible to standard SQL DELETE operations, causing a <SUBSCRIPT> error and halting the purge task.

The correction for this defect is identified as HSDD-6066, which will be included in version 2026.1 and all future product releases. It is also available for older versions via ad hoc change file (patch) or full kit distribution by contacting the Worldwide Response Center (WRC).

Latest Alerts & Advisories

feb. 10, 2026
This problem affects all versions the following products prior to 2025.2:
feb. 10, 2026
This problem affects all versions of Unified Care Record and Information Exchange.