Q: What causes Business Rule Causing Infinite Loop in ServiceNow?

Self-referential Business Rule without workflow protection — Check Business Rules on your affected table for any that update the same record they're triggered on without using current.setWorkflow(false). Look in System Definition > Business Rules and filter by your table name. Cascading Business Rules between related records — Look for Business Rules that update related records (parent/child relationships, reference fields) which then trigger other Business Rules that update the original record. Check both tables involved in the relationship. Business Rule triggering on any field change without conditions — Find Business Rules with 'When' set to 'before' or 'after' update but no 'Condition' field specified. These fire on every field change and may update fields that retrigger the same rule. Multiple Business Rules updating the same field in sequence — Check for multiple Business Rules on the same table with overlapping conditions that update the same fields. Each update can trigger the next rule in an endless chain. Business Rule calling GlideRecord operations without protection — Review Business Rule scripts for GlideRecord.update(), GlideRecord.insert(), or current.update() calls that don't use setWorkflow(false) or proper conditional checks.

Question 1

What causes Business Rule Causing Infinite Loop in ServiceNow?

Accepted Answer

Self-referential Business Rule without workflow protectionhigh likelihood

Check Business Rules on your affected table for any that update the same record they're triggered on without using current.setWorkflow(false). Look in System Definition > Business Rules and filter by your table name.

Cascading Business Rules between related recordshigh likelihood

Look for Business Rules that update related records (parent/child relationships, reference fields) which then trigger other Business Rules that update the original record. Check both tables involved in the relationship.

Business Rule triggering on any field change without conditionsmedium likelihood

Find Business Rules with 'When' set to 'before' or 'after' update but no 'Condition' field specified. These fire on every field change and may update fields that retrigger the same rule.

Multiple Business Rules updating the same field in sequencemedium likelihood

Check for multiple Business Rules on the same table with overlapping conditions that update the same fields. Each update can trigger the next rule in an endless chain.

Business Rule calling GlideRecord operations without protectionlow likelihood

Review Business Rule scripts for GlideRecord.update(), GlideRecord.insert(), or current.update() calls that don't use setWorkflow(false) or proper conditional checks.

Question 2

How do you fix Business Rule Causing Infinite Loop in ServiceNow?

Accepted Answer

How to fix it Navigate to System Definition > Business Rules and filter by your affected table name in the Table field. Identify Business Rules with When set to 'before' or 'after' and Active = true. Open each one that could be involved in the loop. For any Business Rule that updates the current record, add current.setWorkflow(false); before calling current.update() in the Script field. Add field-level conditions to prevent unnecessary triggers. In the Condition field, add checks like current.field_name.changes() to only fire when specific fields change. For GlideRecord operations in Business Rules, add gr.setWorkflow(false); before gr.update() calls where gr is your GlideRecord object. Add execution tracking for complex scenarios by adding this at the start of your Business Rule script: if (gs.getProperty('sys.br.depth', 0) > 5) return; Check for cascading updates between related records. If updating parent records from child Business Rules, add conditions like if (!current.parent.nil()) { parent_gr.setWorkflow(false); } Save all modified Business Rules and test by creating or updating a record of the affected type. If the issue persists, temporarily deactivate suspicious Business Rules one by one by setting Active = false until you identify the specific rule causing the loop.

Question 3

How do you prevent Business Rule Causing Infinite Loop in ServiceNow?

Accepted Answer

Always add current.setWorkflow(false) before any current.update() or GlideRecord.update() calls in Business Rules to prevent workflow chain reactions. Use field-level conditions like current.field_name.changes() in Business Rule Condition fields instead of letting rules fire on every update. Implement execution depth tracking with gs.getProperty('sys.br.depth') checks to prevent runaway recursion in complex Business Rule scenarios. Review Business Rule execution order by setting Order values and ensuring rules that must run together have proper sequencing and exit conditions. Test all Business Rules in a sub-production instance first, especially when they involve cross-table updates or reference field modifications.

Business Rule Causing Infinite Loop in ServiceNow

Symptom

Possible Causes

Debugging this in a real instance?

Solution

How to fix it

Prevention Tips

Test Your Knowledge

Related Articles