You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the Bug:
When setting the unacknowledged alert limit to -1 in the System Limits settings, the system erroneously displays an alert limit reached notification. Though the functionality of allowing unlimited alerts with -1 works correctly, the user interface persists in displaying the error notification.
Steps to Reproduce:
Go to 'Admin'.
Click on 'System Limits'.
Set 'Unacked Alert Limit' to -1.
Navigate to any service, observe the error notification despite it should indicate unlimited alerts due to the -1 setting.
Expected Behavior:
When setting the alert limit to -1, the user interface should not show an alert limit exceeded notification.
Observed Behavior:
Despite setting the alert limit to -1, an alert limit exceeded notification is displayed in the user interface.
Application Version:
This issue is not version or browser specific, it affects all versions and browsers.
Additional Context:
The bug seems to stem from the user interface or warning/notification code performing a count >= limit check without taking the -1 value into account.
The text was updated successfully, but these errors were encountered:
Describe the Bug:
When setting the unacknowledged alert limit to
-1
in the System Limits settings, the system erroneously displays an alert limit reached notification. Though the functionality of allowing unlimited alerts with-1
works correctly, the user interface persists in displaying the error notification.Steps to Reproduce:
-1
.-1
setting.Expected Behavior:
When setting the alert limit to
-1
, the user interface should not show an alert limit exceeded notification.Observed Behavior:
Despite setting the alert limit to
-1
, an alert limit exceeded notification is displayed in the user interface.Application Version:
This issue is not version or browser specific, it affects all versions and browsers.
Additional Context:
The bug seems to stem from the user interface or warning/notification code performing a count >= limit check without taking the
-1
value into account.The text was updated successfully, but these errors were encountered: