How can I track down what Business Rule has been triggered without any log statements?

Maxwell3 · ‎03-16-2023

Hello all,

Is there a way to track down what Business Rule has been triggered in the logs? I don't have any log statements in the BR, and I am trying to find out if a specific Business Rule was triggered.

Ratnakar7 · ‎03-16-2023

Hi @Maxwell3 ,

Yes, you can track down what Business Rule has been triggered in the logs. Here are the steps you can follow:

Identify the table on which the Business Rule is triggered. For example, if you suspect that a Business Rule is triggered when a record is inserted or updated in the Incident table, then that is the table you need to focus on.
Look for any recent activity on that table in the system logs. You can filter the logs by table name, activity type, and time frame to narrow down the search.
Once you have identified the relevant logs, look for any entries that contain the name of the Business Rule. By default, the logs will include the name of the Business Rule that was triggered, as well as the table and the activity that triggered it.
If you are still unable to identify the Business Rule from the logs, you can try enabling debug logging for Business Rules. This will provide more detailed information about the Business Rules that are being triggered. To enable debug logging, go to System Logs > Debugging, and set the log level for Business Rules to "Debug".
Finally, you can also try using the "Table Watcher" plugin in ServiceNow to monitor the activity on the table and identify the Business Rule that is triggered. The Table Watcher plugin allows you to set up a filter for a specific table and view real-time updates as records are inserted, updated, or deleted.

If my response helps you to resolve the issue close the question by ✅Accepting solution and hit 👍thumb icon. From Correct answers others will get benefited in future.

Thanks,

Ratnakar

View solution in original post

WillardLe · ‎05-22-2025

That's a great question—tracing which business rule got triggered can be tricky, especially when dealing with complex workflows in ServiceNow. I usually set breakpoints in scripts or use logs to narrow it down, but sometimes even that isn’t enough. On a related note, when I’m trying to evaluate how businesses handle tricky backend issues (or just customer service in general), I check out sites like PissedConsumer. It’s been surprisingly helpful for getting the bigger picture of how companies manage tech and support challenges.