ARSlisters, 

I have an unmodified OOB escalation in ITSM that should run, but is 'turned
off'.

It starts the notification process after a survey is created in "SRM:Survey"

 

LOG:

/* Checking "SRM:SRV:TriggerSurveyNotification" (enabled) : is turned off

/* Checking "SRM:SRV:TriggerSurveyNotification" (enabled) : going to fire
in 3563

 

ENVIRONMENT

ARS/ITSM 9.1.x

Single server

Escalations enabled in AR Server Admin console AND in ar.cfg

Escalation threads min = 6, max =6

Pool NULL or 1 (no impact)

 

All other escalations are running, just this one is 'turned off'.

 

We built a copy of this escalation ("SRM:SRV:TriggerSurveyNotification2")
and got the same result.

We now have 2 escalations 'turned off'; the unmodified OOB original and our
'custom' duplicate.

Could this be FORM-related?

 

Anyone have any idea what's stopping these escalations?

TIA,

Joel

Joel Sender  *   jdsen...@earthlink.net  

 



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
-- 
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/listinfo/arslist

Reply via email to