Q: What causes Business Rule Not Firing in ServiceNow?

'When' setting doesn't match the operation being performed — Navigate to System Definition > Business Rules and open your rule. Check the 'When' field - if set to 'before insert' but you're updating existing records, it won't fire. The operation must match what you're actually doing. Condition filter is preventing execution — In the Business Rule form, look at the 'Condition' field and 'Filter Conditions' tab. The condition may be too restrictive or referencing fields that don't have the expected values when the rule tries to run. Advanced checkbox not selected when using custom scripts — If you have code in the 'Script' field but the 'Advanced' checkbox is unchecked, the script won't execute. Check the Business Rule form - Advanced must be checked to run custom JavaScript. Business Rule is running on wrong table — Check the 'Table' field in your Business Rule. If it's set to a parent table like 'Task' but you need it to fire on 'Incident', it may not execute as expected due to table hierarchy. Another Business Rule is aborting the transaction — Look in System Logs > System Log > All for JavaScript errors or 'abort action' messages. Check other Business Rules on the same table with higher order values that might be calling gs.addErrorMessage() or action.setAbortAction(true).

Question 1

What causes Business Rule Not Firing in ServiceNow?

Accepted Answer

'When' setting doesn't match the operation being performedhigh likelihood

Navigate to System Definition > Business Rules and open your rule. Check the 'When' field - if set to 'before insert' but you're updating existing records, it won't fire. The operation must match what you're actually doing.

Condition filter is preventing executionhigh likelihood

In the Business Rule form, look at the 'Condition' field and 'Filter Conditions' tab. The condition may be too restrictive or referencing fields that don't have the expected values when the rule tries to run.

Advanced checkbox not selected when using custom scriptsmedium likelihood

If you have code in the 'Script' field but the 'Advanced' checkbox is unchecked, the script won't execute. Check the Business Rule form - Advanced must be checked to run custom JavaScript.

Business Rule is running on wrong tablemedium likelihood

Check the 'Table' field in your Business Rule. If it's set to a parent table like 'Task' but you need it to fire on 'Incident', it may not execute as expected due to table hierarchy.

Another Business Rule is aborting the transactionlow likelihood

Look in System Logs > System Log > All for JavaScript errors or 'abort action' messages. Check other Business Rules on the same table with higher order values that might be calling gs.addErrorMessage() or action.setAbortAction(true).

Question 2

How do you fix Business Rule Not Firing in ServiceNow?

Accepted Answer

How to fix it Navigate to System Definition > Business Rules and open your Business Rule. Verify the When field matches your operation. If you're updating existing records, use before update or after update. If creating new records, use before insert or after insert. Check if the Table field matches the exact table where you're saving records. If you need it to run on Incidents, select Incident [incident], not the parent Task table. Verify the Active checkbox is checked and the Order field has a reasonable value like 100 (lower numbers run first). If you have custom JavaScript code, ensure the Advanced checkbox is checked. Without this, any code in the Script field will be ignored. Review the Condition field. If it contains a script like current.state == 2, test if this condition is actually true when you save the record. Click the Filter Conditions tab. If you have filters set up, verify they match the actual field values on your test record. Add debugging to your script. At the top of your Business Rule script, add gs.info('BR firing: ' + current.number); to verify it's actually running. Save the Business Rule and test by creating or updating a record that should trigger it. Check the logs by navigating to System Logs > System Log > All to see if your debug message appears or if there are any JavaScript errors.

Question 3

How do you prevent Business Rule Not Firing in ServiceNow?

Accepted Answer

Always test Business Rules in a development instance first and verify they work with sample data that matches your production scenarios. Use descriptive names for Business Rules that include the table name and trigger condition, like 'INC - Auto-assign on Priority Change - Before Update'. Document your condition logic in the rule's description field, especially complex filter conditions that might be forgotten later. Set up a standard debugging pattern with gs.info() statements that can be easily enabled/disabled for troubleshooting. Check existing Business Rules on the same table before creating new ones to avoid conflicts and understand the execution order.

Business Rule Not Firing in ServiceNow

Symptom

Possible Causes

Debugging this in a real instance?

Solution

How to fix it

Prevention Tips

Test Your Knowledge

Related Articles