Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

PA Threshold Notification Triggers

tonemking
Giga Expert

The logic is simple when adding a threshold of "Less Than (some number)" or vice versa. However, when adding a threshold of say "less than 1000". If the next collection job runs and inserts a value less than 1000 a notification will/should trigger. An issue I am having is that this notification trigger is not consistent. Sometimes I can get it to work and sometimes I cant.


Scenario

Set up Threshold = Less than 1000 add myself as a recipient

Job   = Collect on table X daily 5:00 AM

Lets just say the past couple weeks every day was above 1000 so if the collection runs at 5:00 AM today relative (one day behind) and the inserted value is 0 or less than 1000 a notification should fire. If that is so I am not sure why this is not working. Any insight on Thresholds ? I understand the event pa.job.threshold.reached are controlled by three business rules in the background and "Pa Threshold reached" is the notification going out.


Theoretically I should be able to delete scores for an indicator and recollect, therefore re firing this notification on demand or am I wrong?

Anyone else having this problem because I am banging my head on my desk as we speak? I am working in a developer instance on Geneva.

1 ACCEPTED SOLUTION

tonemking
Giga Expert

So it looks like I was able to get them to fire and the logs show that the notifications went out at 18:00 hours. What is interesting is that when I tested in the past successfully the notifications went out at the same time. The last job I executed was at 11 AM so it seems the trigger is set on a delay.


View solution in original post

1 REPLY 1

tonemking
Giga Expert

So it looks like I was able to get them to fire and the logs show that the notifications went out at 18:00 hours. What is interesting is that when I tested in the past successfully the notifications went out at the same time. The last job I executed was at 11 AM so it seems the trigger is set on a delay.