Group Manager Vector events (500 — 999)

Last Updated : Dec 08, 2021 |
Prolog information
Metadata
Keywords:
Group Manager Vector events are listed in the following table:
Group Manager Vector Events (500 — 999)
EventType
Event Description, as it is displayed on the event log (keyword)
Explanation
Event Data 1
Event Data 2
520
Split queue is full
A queue-to split, check split, or messaging split command is executed, but the call did not queue to the split because the queue is full. To prevent this condition, use a “goto step...if calls queued in split...>...” before each queue-to split or check split step so that an alternative treatment can be provided for such cases.
Hunt group number
Call ID
521
Not vector-controlled
The split accessed by a queue-to split or check split command is not vector-controlled. As a result, the step is skipped.
Hunt group number
Call ID
522
AAS split cannot queue
A queue-to split, check split, or messaging split command is executed on an AAS, but the call did not queue to the split because all the agents are logged out by RONA.
Hunt group number
Call ID
540
AUDIX link down
Messaging system cannot be accessed using a messaging split command because the messaging-system link is down. As a result, the step is skipped.
Hunt group number
Call ID
541
Not a messaging split
The split administered for the messaging split command is not a messaging split, that is, the split does not have a messaging type administered. As a result, the step is skipped.
Hunt group number
Call ID
542
Can’t connect idle agent
The call at the head of the queue cannot be connected to an idle agent.
Hunt group number
Call ID
550
ASA - No staffed agents
A check or goto test requested a comparison of ASA for a split or skill that has no staffed agents. The comparison was based on ASA > largest possible threshold.
Hunt group number
Call ID
560
EWT no history for split
A goto test requested EWT for a split or skill that has not yet acquired history. The wait time is the default value.
Hunt group number
Call ID
561
EWT no split queue
A goto test requested EWT for a split or skill that has no queue. The wait time is treated as infinite. The comparison is based on EWT > largest possible threshold.
Hunt group number
Call ID
562
EWT split queue full
A goto test requested EWT for a split or skill, the queue, of which, is currently full. The wait time is treated as infinite. The comparison is based on EWT > largest possible threshold.
Hunt group number
Call ID
563
EWT split no working agents
A goto test requested EWT for a split or skill that has no agents logged in or all logged in agents are in the Aux work mode. The wait time is treated as infinite and the comparison is based on EWT > largest possible threshold.
Hunt group number
Call ID
564
EWT split locked
A goto test requested EWT for a split or skill that is currently locked. The wait time is treated as infinite. The comparison is based on EWT > largest possible threshold.
Hunt group number
Call ID
565
EWT call no working agents
A goto test for a call or converse data passing wait requested EWT for a call that is queued only to splits or skills that have no agents logged in or that have all logged in agents in the Aux work mode. In this case, the wait time is treated as infinite and the comparison is based on EWT > largest possible threshold.
Hunt group number
Call ID
Related links
Denial events