- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-14-2025 04:59 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-14-2025 06:43 AM
Hi @KannigaP ,
You can check for custom business rules with script contains "setWorkflow(false)" which can also cause the issue.
There could be several reasons why a business rule is not triggering when a record is inserted into a table in ServiceNow. Here are some possible causes and solutions:
1. **Business Rule is Inactive**: Ensure that the business rule is active. You can check this by navigating to the business rule and checking the 'Active' checkbox.
2. **Incorrect Filter Conditions**: The conditions specified in the business rule may not be met. Check the 'When to run' section of the business rule and ensure that the conditions are correct.
3. **Order of Execution**: The order in which the business rule is executed may be causing the issue. If there are other business rules on the same table, they may be affecting the record before your business rule runs. You can change the order of execution by modifying the 'Order' field in the business rule.
4. **Incorrect Table**: The business rule may be on the wrong table. Ensure that the business rule is on the correct table.
5. **Script Errors**: There may be errors in the script that is being run by the business rule. Check the script for any errors and correct them.
6. **Access Control**: There may be access control rules that are preventing the business rule from running. Check the access control rules for the table and ensure that they are not preventing the business rule from running.
7. **Debugging**: Use the Debug Business Rules module to see if the business rule is being triggered and to identify any issues.
8. **Async Business Rule**: If it's an asynchronous business rule, there might be a delay in execution. Check the system logs to see if the rule has been executed.
Remember to test any changes in a sub-production instance before applying them to your production instance.
Reference : https://www.servicenow.com/community/developer-forum/business-rule-doesn-t-trigger-when-record-is-in...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-14-2025 06:43 AM
Hi @KannigaP ,
You can check for custom business rules with script contains "setWorkflow(false)" which can also cause the issue.
There could be several reasons why a business rule is not triggering when a record is inserted into a table in ServiceNow. Here are some possible causes and solutions:
1. **Business Rule is Inactive**: Ensure that the business rule is active. You can check this by navigating to the business rule and checking the 'Active' checkbox.
2. **Incorrect Filter Conditions**: The conditions specified in the business rule may not be met. Check the 'When to run' section of the business rule and ensure that the conditions are correct.
3. **Order of Execution**: The order in which the business rule is executed may be causing the issue. If there are other business rules on the same table, they may be affecting the record before your business rule runs. You can change the order of execution by modifying the 'Order' field in the business rule.
4. **Incorrect Table**: The business rule may be on the wrong table. Ensure that the business rule is on the correct table.
5. **Script Errors**: There may be errors in the script that is being run by the business rule. Check the script for any errors and correct them.
6. **Access Control**: There may be access control rules that are preventing the business rule from running. Check the access control rules for the table and ensure that they are not preventing the business rule from running.
7. **Debugging**: Use the Debug Business Rules module to see if the business rule is being triggered and to identify any issues.
8. **Async Business Rule**: If it's an asynchronous business rule, there might be a delay in execution. Check the system logs to see if the rule has been executed.
Remember to test any changes in a sub-production instance before applying them to your production instance.
Reference : https://www.servicenow.com/community/developer-forum/business-rule-doesn-t-trigger-when-record-is-in...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-14-2025 07:30 AM
Hi Sandeep,
Thanks for the quick response. There was a custom Before Insert/Update business rule with setWorkflow(false) in the order of 50, which was terminating the after insert BR executions. Deactivated that BR which solved the issue. Thank you so much!