Having a problem with a Notification Policy
I've been scratching my head on this for a while now and though maybe someone could help me figure out the problem.
I will have indicents that will be set with certain conditions; namely a Priority of Scheduled Task, a Status of Hold, and a Due date set for the future. What I want to do is set a condition that on the day after the due date, I want to change the status and priority of the ticket becasue it now needs to be completed.
I know the way to do this is with a Notification Policy. I have one that closes incidents in a Resolved status if they have not been modified in 72 hours. This one should be really no different in terms of the "what to do", but for some reason, the policy won't execute on a scheduled basis.
Here is the SQL query I'm using. It does return the information I expect:
SELECT DISTINCT
hd1.[workitem_number] AS 'Ticket_number',
hd1.[workitem_due_on] AS 'Due',
getdate() AS 'Today',
datediff (hh,hd1.[workitem_due_on],getdate())as 'Difference'
FROM dbo.HD_workitem_current_view hd1
WHERE hd1.[workitem_status_lookup_id] = 500
AND hd1.[workitem_priority_lookup_id] = 125
AND datediff(hh, hd1.[workitem_due_on], getdate()) >= 24
(Was using hours at this point as a troubleshooting means. Did try using days and have the exact same result)
I then created an Edit incident Automated Action to make the changes:
Bottom portion of the Action:
The issue is when I create a schedule to run this policy, the time comes and goes and the incident doesn't get modified. HOWEVER, if I have an incident that does meet the criteria and I click the Test Notification Policy button, it works.
Any thoughts on where I coud look to resolve this issue?
Comments
Check Time Zones
Greetings,
Check your time zone on your SQL Server and make sure that both the time zone and time/date matches on both your NS/Helpdesk and SQL Servers. The issue seems to be schedule related since it works when you manually run it.
Time Zone not an issue
Thanks for the advice mabdelnabi, but in my case, my NS/helpdesk and SQL server is on the same box so there is no time zone issue.
I do agree with you that the likely culprit is a scheduleing issue, but the thing that bothers me is the fact that other scheduled events are running normally.
I may have to contact Support on this unless there are some other suggestions of places I could look.
RE: Time Zone not an issue
Hi John,
Are you able to post a screen-shot of your schedule itself?
Would you like to reply?
Login or Register to post your comment.