Legacy Dev Forum Posts

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Additional 5 second Bullseye ring in Queue Details

  • 1.  Additional 5 second Bullseye ring in Queue Details

    Posted 06-05-2025 18:27

    Cory_King1 | 2023-07-25 13:15:05 UTC | #1

    Hi Dev Forum - While pulling queue data from /api/v2/routing/queues/{queueId}, I noticed that queues that are using Bullseye Routing include an additional object for TIMEOUTSECONDS with a Threshold equal to 5 seconds. This additional object is not visible on the Queue>Routing tab in the UI. Does anyone know the significance of the extra TIMEOUTSECOND segment? I can't seem to find anything in the API documentation, but may have overlooked what I'm searching for. I've included an example below on a queue that is removing 1 skill after 90 seconds.

    Thank you, Cory

    "bullseye": { "rings": [ { "expansionCriteria": [ { "type": "TIMEOUTSECONDS", "threshold": 90 } ], "actions": { "skillsToRemove": [ { "name": "REDACTED", "id": "952877a9-63a8-4792-8747-529df86e3ba3", "selfUri": "/api/v2/routing/skills/952877a9-63a8-4792-8747-529df86e3ba3" } ] } }, { "expansionCriteria": [ { "type": "TIMEOUTSECONDS", "threshold": 5 } ] } ] },

    jacobshaw | 2023-07-26 13:37:22 UTC | #2

    Hi @Cory_King1 The timeout is an evaluation criterion representing the time that should elapse before the evaluation moves into the next bullseye ring. As seen in the response schema in the API explorer.

    I'm not sure it makes sense to have two timeouts for the same ring. You could update the queue to only use one timeout using PUT /api/v2/routing/queues/{queueId}

    Cory_King1 | 2023-07-26 13:50:38 UTC | #3

    Thanks @jacobshaw - I understand that this is the criterion before moving on to the next bullseye ring, but when I set up a queue with Bullseye routing, there is an additional 5 timeout seconds that the system creates. So, in the UI, I fill out the information to create one bullseye ring to be evaluated for 90 seconds and I can see this in the JSON payload:

    { "expansionCriteria": [ { "type": "TIMEOUT_SECONDS", "threshold": 90 } ], "actions": { "skillsToRemove": [ { "name": "REDACTED", "id": "952877a9-63a8-4792-8747-529df86e3ba3", "selfUri": "/api/v2/routing/skills/952877a9-63a8-4792-8747-529df86e3ba3" } ] } },

    But also in the API call is this segment in the JSON: { "expansionCriteria": [ { "type": "TIMEOUT_SECONDS", "threshold": 5 } ] } ] },

    The additional 5 second ring is not visible in the UI, so I'm wondering what the purpose of this segment is. Do you have any insight?

    Thanks, Cory

    jacobshaw | 2023-07-26 14:17:17 UTC | #4

    I've tested this on my end and was able to reproduce the same behavior. This is potentially a bug. Please open a case with Genesys Cloud Customer Care to determine if this is something that needs to be fixed

    Cory_King1 | 2023-07-26 14:49:33 UTC | #5

    Thanks, @jacobshaw - I'll reach out to Care. I appreciate the guidance!

    Cory

    system | 2023-08-26 14:50:17 UTC | #6

    This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.

    This post was migrated from the old Developer Forum.

    ref: 21142



Related Content