Known and corrected issues
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 |
|---|---|---|---|---|
| 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 |
| API | The Metrics Ingestion API intermittently returns HTTP 500 status codes. This leads to failed telemetry data ingestion, resulting in incomplete or missing metrics and potential monitoring gaps. | Fixed in 25.3 | 25.2.01 | DRTOM-43829 |
| PATROL Agent | PATROL Agents that go down unexpectedly continue to appear as connected in BMC Helix Operations Management. As a result, no Self-Monitoring event is triggered for these agents. | Fixed in 25.3 | 25.2.01 | DRTOM-43821 |
| Events | When a non-administrator user tries to export multiple events, the generated file, regardless of the selected format, is empty (zero bytes). Therefore, users are unable to retrieve event data, affecting reporting and analysis workflows. | Fixed in 25.3 | 25.2 | DRTOM-43714 |
| Authorization profile | If a user group that is associated with an authorization profile is deleted, you cannot edit or delete the authorization profile. | Fixed in 25.3 | 25.2.01 | DRTOM-43273 |
| Events | Events generated on off-boarded tenants are processed, resulting in incorrect situations and health score computation. | Fixed in 25.3 | 25.2 | DRTOM-43114 |
| Event policies | The lookup function in an event policy does not work if events with the same ID are generated without an interval between them. | Fixed in 25.3 | 25.2.01 | DRTOM-43103 |
| Event policies | The DDEN policy takes a long time to run. | Fixed in 25.3 | 25.2 | DRTOM-43091 |
| Alarm policies | On the BMC Helix Operations Management user interface, incorrect messages are displayed when an alarm policy is created with the threshold, violate baseline, and metric violates baseline options. | Fixed in 25.3 | 24.4 | DRTOM-42094 |
| Groups | While creating a group, if you select the within operator, you can see incorrect options for further selections. | Fixed in 25.3 | 25.1 | DRTOM-41987 |
Related issues
The following links provide information about issues in the integrated BMC Helix products.