When trying to publish your changes made to your configuration, you might be presented with some warnings if any incorrect configuration is detected. This article will explain the possible error messages you can see, and how to remedy them.
The following warning will be displayed.
Followed by the affected Group
or Device
Click on the grey box containing the Group/Device to expand the error message, and see what action needs to be taken. The name in green can be clicked to be taken directly to the page for the offending configuration.
no-group-with-0-escalation-levels-P1
Group has no escalation levels. All groups must have a minimum of one escalation level.
The affected Group has no escalation levels set. Please edit the escalation to ensure there is at least one designated escalation level.
Cause
There are no escalation levels configured for this Group.
Solution
Add an escalation level for this Group.
no-escalation-levels-with-0-targets-P1
Escalation level number {sequence} doesn't send alerts to any groups.
Cause
There is an escalation level added, but it does not contain any information on which Group(s) need to receive the alert.
Solution
Assign one or more Group(s) to this escalation level, or delete it. Please note that if this is the only escalation level, it should not be deleted.
no-escalation-levels-after-target-all-groups-P1
Escalation level number {sequence} alerts one (or more) groups, but a preceding escalation level will have already sent the alert to all groups.
Cause
An escalation level is alerting a Group that has already been alerted through a previous escalation level set to alert All Groups.
Solution
Either remove the escalation level alerting the single Group, or change the escalation alerting All Groups to a selection that does not include the previously alerted Group.
no-repeat-a-target-P1
Escalation level number {sequence} alerts a group that will have already been alerted by a preceding escalation level.
Cause
The designated escalation level is alerting a Group that has already been included in a previous escalation level.
Solution
Remove either of the duplicate assignments from one of the escalation levels.
no-repeat-a-target-P2
Escalation level number {sequence} alerts all groups but a preceding escalation level will have already done so.
Cause
The designated escalation level is alerting All Groups, but a previous escalation level is already configured to alert All Groups.
Solution
Either change the preceding escalation level(s) to not alert All Groups, or remove the duplicate mention of All Groups from the escalation level following the first.
no-repeat-a-target-P3
Escalation level number {sequence} alerts all locations not assigned to a group, but a preceding escalation level will have already done so.
Cause
The designated escalation level is alerting Locations not in a Group, but a previous escalation level is already configured to alert Locations not in a Group.
Solution
Either change the preceding escalation level(s) to not alert Locations not in a Group , or remove the duplicate mention of Locations not in a Group from the escalation level following the first.
no-device-portable-with-1-location-P1
"Prompt for location" is ticked but the device is used at a single location. Either untick "Prompt for location" or add additional locations.
Cause
The device mentioned is assigned to a single location, but only configured to prompt for location.
Solution
Either untick the checkbox next to Prompt for location on this device, or assign more locations to this device.