Business rule not being triggered
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2016 05:14 PM
I have a custom table that we created and I created a Business Rule to run on this table. Regardless of what I try I can not get the BR to trigger. I have turned on debugging for Business Rules and the BR is not even being triggered. Screen shots are below. Has anyone seen this before? It is a very odd issue.
- Labels:
-
Scripting and Coding

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2016 05:55 PM
I had this exact same issue after an upgrade from Fuji to Geneva, where a business rule was inexplicably not being triggered. The only thing the fixed it was the solution I provided and I was not able to reproduce it ever again!
When you create a new onBefore business rule, what is the default code?
Things to try:
- Change the function name in the closure to onBefore
- Create a new business rule, copying the code from inside your function into a new function (leave the default function declaration)
- Check the value in the condition field (right click -> show xml). It could be filled with junk?
ServiceNow Nerd
ServiceNow Developer MVP 2020-2022
ServiceNow Community MVP 2019-2022
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-12-2016 10:19 AM
I reached out to Hi support and they found the problem. They opened a problem ticket for it. Basically the business rule has to be created on the global domain if it is for a scoped application, we have domain separation setup and I created the BR on one of the sub domains.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-03-2020 07:59 AM
I faced a similar issue where I could figure out what was causing the BR to not work. One of the field was showing as invalid update - an error message (a email type field). After making the change it worked.
There was no BR which had setWorkflow false or the scope issue