Skip Navigation
Expand
Round Robin incident assignment
Answer ID 11143   |   Last Review Date 10/07/2021

Why was an incident, with a Round Robin queue, not assigned to an available agent?

Environment:

Oracle B2C Service, Round Robin incident routing

Resolution:

When using Round Robin, the following is required for assignment to occur:
  1. Incident Queue is set to a Round Robin queue  (as specified by the Customizable Menus editor, system menus -> Incident Queues). "Round Robin (Logged In)" has additional requirements listed below and Round Robin-All has less requirements. 
  2. An agent's profile has the Round Robin Incident Queue selected under Service tab -> Incident Queues
  3. The agent's incident Inbox Limit has not been reached 
  4. The incident status type is Unresolved (Round Robin will not assign out Solved or Waiting status types)
  5. For "Round Robin (Logged In)" only:
    1. The agent is logged in for that profile
    2. The dbstatus -r utility must run. This generally runs every 15 minutes. Thus, it can take up to 15 minutes for a new incident to be assigned out when using Round Robin (Logged In). 
    3. If the agent's inbox is full and they close out one of their incidents, this will also trigger the utility to assign out an available incident (up to the number set in the agent's Pull Quantity or Inbox Limit whichever is reached first). 

For more information about setting up Incident Queues, refer to the Add or Edit an Incident Queue section of online documentation. 

For more information about Profile Incident Queue settings, refer to the Assign Service Permissions section of online documentation.

To access Oracle B2C Service manuals and documentation online, refer to the Documentation for Oracle B2C Service Products.