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
We need to implement a mechanism for detecting deadlocks during rule execution. This occurs when a rule triggers and the application responds by requesting the rules to be executed again.
Proposal
Our expectation is that rules should operate continuously; however, if the same rule executes more than a specified number of times (N) with performing the same operation, it should raise an exception and stop executing that rule but continue to others. This exception should include debug information, such as the fact name and, if possible, a trace.
This solution could significantly enhance the stability and robustness of our user interface, especially in cases of poorly written code or unexpected scenarios.
The text was updated successfully, but these errors were encountered:
Context
Hello,
We need to implement a mechanism for detecting deadlocks during rule execution. This occurs when a rule triggers and the application responds by requesting the rules to be executed again.
Proposal
Our expectation is that rules should operate continuously; however, if the same rule executes more than a specified number of times (N) with performing the same operation, it should raise an exception and stop executing that rule but continue to others. This exception should include debug information, such as the fact name and, if possible, a trace.
This solution could significantly enhance the stability and robustness of our user interface, especially in cases of poorly written code or unexpected scenarios.
The text was updated successfully, but these errors were encountered: