Skip to Content

Issues table

Review the following tables for issues that were corrected in BMC Helix AIOps 25.1 and for known issues that remain open.

Corrected issues

View the issues in the following table by the default sort order, Corrected in, which shows the corrected issues first. 

The version number represents the update (Year.Month.Release) or release number (MajorRelease.MinorRelease.ServicePack.Patch) in which the issue is fixed.

Known (open) issues

To view only the open issues, click the Corrected in filter, and select empty. An issue without a value for Corrected in remains open.

You can also filter and sort issues according to the affected version (versions in which the issue exists), component, or defect ID.

Related topics

Release-notes-and-noticesBMC Helix Portal Known and corrected issues

ComponentDescriptionCorrected inAffected versionsDefect ID
Overview page > Time range selectorOn the Overview page, if one of the dates from the time range selector (From or To) falls on a date where Daylight saving time (GMT+/- 01:00) is observed, a lag or lead of an hour is shown in either of the time range selector fields. This lead or lag does not affect the process of retrieving data from the backend. Data retrieval is performed based on the epoch time. 24.4.x, 25.1.00, 25.1.01, 25.2DR0F3-17246
Situations

Symptom: The situation summary displays the following message: Unknown Issue. The Situation began with an unknown event, which caused an unknown event.

Scope: When the root cause event for a situation is deleted from BMC Helix Operations Management, the situation summary generated by BMC HelixGPT is unable to provide the root cause and summary of the issue for the event. No root cause event is displayed for the situation. 

 24.3.x, 24.4.x, 25.1.00, 25.1.01, 25.2DR0F3-15859
Incidents for situations

Symptom: The Situation is stabilized and no new events will be added now. message is not displayed for a situation event in the Logs and Notes tab in BMC Helix Operations Management. 

Scope: After a situation is stabilized based on the stabilization window, the message - Situation is stabilized and no new events will be added now is displayed in the Logs and Notes tab. However, if a primary and a similar situation are formed at the same time, sometimes this message is not displayed. This does not affect the behavior of the situation. 

 24.2.x, 24.3.x, 24.4.x, 25.1.00, 25.1.01, 25.2 
Incidents for situations

Symptom: Related situations show incident ID, but no incident ID is displayed in the primary situation. 

Scope: If the incident is created for a situation after a primary situation is formed, then the primary situation does not show the incident ID. 

 24.2.x, 24.3.x, 24.4.x, 25.1.00, 25.1.01, 25.2DR0F3-12106
Incidents for situations

Symptom: A single causal CI host name is displayed in the incident created for ML-based situations in BMC Helix ITSM. 

Scope: If a situation has multiple root cause events, the incident includes the CI details of only one of them. 

 24.2.x, 24.3.x, 24.4.x, 25.1.00, 25.1.01, 25.2 
Situations > Similar Situations

Symptom: Not all closed situations are displayed in the group of similar situations.

Scope: Situations that are closed manually before saturation are not considered for grouping.

 23.2.x, 23.3.x, 23.4.x, 24.1.x, 24.2.x, 24.3.x, 24.4.x, 25.1.00, 25.1.01, 25.2DR0F3-5219

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Helix AIOps 25.2