Alert priority breakdown score of Application Services is 0Summary<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: block; max-width: ; width: auto; height: auto; } } If the alert priority breakdown score of Application Services is 0, then there could be several possible reasons for this: • There are no impacted services. • One or more services are impacted, but the em_alert_priority_category_mapping table is not aligned with the customisation of the service’s business criticality. If the business-criticality values were customised differently from the out-of-box (OOB) values, the same need to be updated in the em_alert_priority_category_mapping accordingly. Note: Any customisation of em_alert_priority_category_mapping or em_alert_priority_ci_type applies only to alerts that are created or updated after the customisation. Existing alerts are not affected.