Why an SLA Event status is set to Status 4 - Unknown -

Document ID : KB000121476
Last Modified Date : 22/11/2018
Show Technical Document Details
Introduction:
Why an SLA event is set to status "4 - Unknow" in some circumstaces?
Question:
Why an SLA event is set to status "4 - Unknow" in some circumstaces?
Environment:
Service Desk Manager 14.x/17.x
Answer:
The SLA event may be set to status 4 - Unknow for the following reason: 

In bopevt.maj: 

JMC - consider using a table here 
status_flag INTEGER { 
ON_NEW DEFAULT 2; 
}; 
// 0 is canceled 
// 1 has fired 
// 2 is waiting to fire first time 
// 3 is waiting to fire 'next' time 
// 4 hosed in some way. << ############ 

"Hosed means - Messed up completely and without hope; to be in a hoplessly bad condition or position." 
So that's why the status is set to Unknown.