IT CanvassTalk to an advisor
ServiceNow Troubleshooting · LessonReviewed by Sneha I, ServiceNow Trainer, 8 yrs · Updated · Published · current release · fixes

ServiceNow Debugging business rules

Why a rule did not fire, and how to find out.

Quick answer

When a ServiceNow business rule misbehaves, check five things before rewriting it: that the when, before, after or async, and the condition both match the case; the order field, since a lower-order rule may change the data first; gs.info() logging against the system log; that the rule is active and in the right scope; and recursion from current.update().

When a business rule misbehaves, work through this checklist.

  • Confirm the When (before/after/async) and the condition match.
  • Check the order field, a lower-order rule may change data first.
  • Add gs.info() logging and watch the system log.
  • Verify the rule is active and in the right scope.
  • Watch for recursion from current.update().
Try it YourselfJavaScript
▸ Press Run to execute.

Runs in a sandbox in your browser. Mock gs and GlideRecord and sample data are provided.

Practise this on your own free instance.
Set up your free instance →
Already working on ServiceNow and stuck on a live ticket?Get an expert ServiceNow developer on screen-share to finish your daily tasks with you. Deliver on time, protect your reputation and your job. Monthly support only, no task-wise plans.Task assigned · no idea where to startStill stuck · your job on the lineExpert joins your screenDelivered on timeExplore On Job Support