Known and corrected issues
Review the following table for issues that were corrected in BMC Helix Operations Management 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-Day) 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 component or defect ID.
Known and corrected product issues
Component | Description | Status | Found in | Defect ID |
|---|---|---|---|---|
| Groups | When you select a group on the Configuration > Groups page, you can see the following error: | Fixed in 25.4 | 25.3 | DRTOM-46206 |
| Groups | When an Agent tag is deleted from a group that includes a PATROL Agent and remote devices, the Agent tag is removed from the PATROL Agent but remains on the remote devices. As a result, the group shows a total of two devices instead of zero. | Fixed in 25.4 | 25.2 | DRTOM-46525 |
| Event policies | The following error is displayed even after dynamic enrichment policies are applied to events: [Policy sm_case_02046920_dden: 'Unable to enrich as value: %severity% is This issue occurs when the following format is used to enrich an enum value of a slot: %<enum_value>% For example, the error occurs when you use the following format to enrich the CRITICAL enum value: %severity% | Fixed in 25.4 | 25.3 | DRTOM-46429 |
| Event policies | If a user has the core.* permission, they cannot see the Event Policies and Blackout Policies pages in BMC Helix Operations Management. | Fixed in 25.4 | 25.3 | DRTOM-46358 |
| User management | When users are synced from IT Service Management, the user preferences are not saved. | Fixed in 25.4 | 25.2 | DRTOM-46045 |
| Events | The Events page takes a long time to load. | Fixed in 25.4 | 24.3 | DRTOM-45598 |
| Event policies | When you use the matches operator in an event policy, the event lookup fails. | Fixed in 25.4 | 25.3 | DRTOM-45379 |
| Agent Query Tool | When a high number of monitor policies are migrated, the Agent Query Tool (AQT) fails to start. | Fixed in 25.4 | 25.2.02 | DRTOM-45225 |
| API | Even if you send a valid JSON Web Token (JWT) to authenticate a REST API, the msearch REST API intermittently returns an authentication error with the 500 response code. | Open | 25.2.01 | DRTOM-45212 |
| Events | When an IT Service Management incident is created for a BMC Helix Operations Management event, the event ID is not updated correctly in BMC Helix Operations Management with the incident ID. This issue occurs because BMC Helix Operations Management overwrites the worklog ID from IT Service Management because of the out-of-the-box deduplication policy. | Fixed in 25.4 | 25.2.01 | DRTOM-44244 |
| Events | When you create a custom event slot, a used slot number is sometimes assigned to the new slot. | Fixed in 25.4 | 25.2 | DRTOM-42872 |
| Events | When you send events to BMC Helix Operations Management by using the REST API, events are not ingested, and BMC Helix Operations Management times out with the 504 error. | Fixed in 25.4 | 23.2.02 | DRTOM-39979 |
| Events | If events from a time-based event policy and an update API arrive at the same time, events are not updated correctly. | Fixed in 25.4 | 24.4 | DRTOM-39937 |
| Alarm policies | While configuring an alarm policy, if you are using the AND and OR conditions together in the selection criteria without using brackets, the resulting alarm events can be incorrectly generated. Resolution Use brackets if you are using the AND and OR conditions together in the selection criteria. | Open | 25.1.02 | DRTOM-42958 |
Event policies | Error messages for the If action in advanced enrichment policies are not localized in the Chinese and German locale. | Open | 23.1 | DRTOM-27795 |
Event policies | If the permissions are swapped for two restricted users, a user who has role-based access control to view and manage only blackout policies (core.blackout_policies.view and core.blackout_policies.manage permissions) can view event policies as well. | Open | 22.2.01 | DRTOM-21830 |