-
Feature Request
-
Resolution: Unresolved
-
Undefined
-
None
-
2.5
-
False
-
-
False
Request:
Issue:
Rulebook activation fails, and even after attempting a restart, it remains unsuccessful. There is no notification mechanism in place to alert the user. As a result, the user must manually log into the UI to monitor the activation status. By the time the issue is noticed, rules have not been executing during the downtime.
Impact to Business:
Failures in event-driven automation directly lead to system downtime, accumulation of unresolved issues, and significant remediation delays. Since no automated actions occur until the failed rulebook activation is detected and resolved, teams are forced to rely on excessive manual intervention. This not only increases operational overhead but also heightens the risk of delayed responses to critical events.