Execution Order FAILED - AFTER Business Rules with order over 1000 not being triggered

Andrii ICL
Tera Contributor

‎08-09-2024 01:33 AM

Hi Community,

 

very non-trivial situation I've faced recently working on domain-separated environment. Not sure domain separation has something to do with it - but I believe it is important to mention 

 

PROBLEM:

 

All business rules on INSERT operation with order over 1000 are not being executed - even if they have a single line of code to generate log. BEFORE Business Rules or Business Rules are working fine. Also notifications on INSERT are not being triggered

0 Helpfuls
  • 289 Views
2 REPLIES 2

Rajesh Chopade1
Mega Sage

‎08-09-2024 01:58 AM

Hi @Andrii ICL 

there could be several reasons for this issue:

  1. Order Conflict: The order value may be conflicting with other business rules. Ensure no other rule with a lower order value is preventing these rules from running.
  2. Condition or Filter: Check if the conditions or filters in your business rules are too restrictive, causing them not to execute.
  3. Event Queue: For notifications, ensure that events are properly queued. Issues in the event queue can prevent notifications from triggering.
  4. Script Errors: Ensure there are no errors in other parts of the script that could cause the rule to terminate prematurely.
  5. Run Condition: Verify if there are any run conditions that may be affecting the execution, especially if they involve dynamic queries or checks.

Review these areas to identify any potential issues that might be affecting the execution of your business rules and notifications.

 

I hope my answer helps you to resolve your issue,  if yes please mark my answer helpful & correct.

THANK YOU

rajesh chopade.

Simon Christens
Kilo Sage

‎08-09-2024 02:05 AM

Try searching for BRs where script contains setWorkflow
current.setWorkflow(false) will stop BRs from running so if theres a BR using this then it will stop other BRs from running.
If there is no BRs with that then you probably want to look into script includes - if a BR call a script include that uses setWorkflow(false) on the given (or another) record on that specific table then it can interfere with other BRs