High Rate of Unclassified Errors Alert Triggered by Type-Cast Exception in OccultusEventBroker Ingest Path - Support and Troubleshooting

High Rate of Unclassified Errors Alert Triggered by Type-Cast Exception in OccultusEventBroker Ingest Path .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } High Rate of Unclassified Errors

OccultusEventBroker Ingest Path — Typecasting Defect

Article Type

Known Error / Troubleshooting

Applies To

HLA app ≤ 39.0.15 / Occultus ≤ 1.36.0.26

Last Updated

June 2026

Executive Summary Alert root cause: runtime cast exception in the OccultusEventBroker ingest path triggered by smart-parser returning non-string values for reserved fields. Behavior: Transient and data-dependent; alerts typically auto-resolve when the triggering input pattern stops. Immediate action: Identify and disable the parser or input producing non-string values for reserved fields. Permanent fix: Upgrade to HLA app 39.0.16 and Occultus 1.36.0.27 (March 2026 release train).

Root Cause In the affected release lineage, smart-parser output values are stored as generic objects. Certain EventBroker code paths assume those values are always strings. When a parser returns a non-string value for a reserved field, a runtime cast exception is thrown during event handling. Those exceptions are counted as unclassified EventBroker errors, triggering the alert.

The issue is data-dependent — it surfaces only when specific input patterns produce non-string values for reserved fields — which explains why alerts can auto-resolve after the problematic input stops.

Symptoms "High rate of unclassified errors" alert fires on an Occultus-monitored tenant or environment. Exceptions originate in the OccultusEventBroker ingest path. Alert may auto-resolve without manual intervention once the triggering input pattern stops. No persistent data loss expected; processing failures may occur during the affected window.

Mitigation Steps 1. Reduce Exposure to the Failing Parser / Input Pattern Review data inputs and smart-parser behavior during the alert window. Identify any parser returning non-string values for reserved fields. Disable or adjust that parser temporarily until a fixed release is applied. 2. Monitor for Recurrence Continue monitoring Occultus-Node-Health and EventBroker error activity for the affected tenant or environment. If the alert recurs, capture ingest and error logs from the same timeframe to pinpoint the exact parser / data-input combination.

Permanent Fix — Recommended Upgrade Upgrade to the March 2026 release train, which includes improvements and fixes in the smart-parser / cast-exception area that address the defect family associated with these alerts.

Component

Target Version

HLA app

39.0.16

Occultus

1.36.0.27

Related Monitoring Occultus-Node-Health — ongoing node and ingest health. EventBroker error activity — cast exception trends in the ingest path.

If the alert persists after mitigations and an upgrade cannot be scheduled immediately, open a support case and attach ingest/error logs from the alert window for further investigation.