Unfortunately, due to how the API works the only way you can switch from bullseye routing is to have no members associated with those bullseye rings. A way to do this is to remove the `member_groups` attribute of the bullseye rings with members from the queue first and add those group IDs to the `skill_groups` attribute.
For example:
"genesyscloud_routing_queue": {
"test_bullseye_routing_queue": {
"name": "test_bullseye_routing_queue",
"bullseye_rings": [
{
"expansion_timeout_seconds": 2,
"member_groups": {
"member_group_id": "${genesyscloud_routing_skill_group.skillgroup_test_languagesetter.id}",
"member_group_type": "SKILLGROUP"
}
},
{
"expansion_timeout_seconds": 120,
}
]
"skill_groups": [
"${genesyscloud_routing_skill_group.bullseye_testing.id}",
"${genesyscloud_routing_skill_group.test_LanguageSetter.id}"
],
}
},
You can apply this, then after you can remove the bullseye rings entirely and have no API error thrown while still keeping those skill groups in the queue.
"genesyscloud_routing_queue": {
"test_bullseye_routing_queue": {
"name": "test_bullseye_routing_queue",
"skill_groups": [
"${genesyscloud_routing_skill_group.bullseye_testing.id}",
"${genesyscloud_routing_skill_group.test_LanguageSetter.id}"
],
}
},
Once you apply this you will be back to standard routing with the groups still linked to the queue.
Thanks,
Fergal
------------------------------
Fergal McLaughlin
Software Engineer Intern
------------------------------
Original Message:
Sent: 06-02-2025 10:18
From: William Valin
Subject: [BUG?] Error when removing Bullseye routing
Thanks for the reply.
We don't actually intend to delete the group, we're just trying to switch back the queue from Bullseye routing to Standard routing. Is there a way to do this or are we blocked?
------------------------------
William Valin
Original Message:
Sent: 05-29-2025 09:55
From: Fergal McLaughlin
Subject: [BUG?] Error when removing Bullseye routing
Hi again,
I've looked into the issue and can see the error, but this looks to not be an issue with the terraform provider and seems to be intended functionality of the API. Bullseye Rings that have any members associated with them (in this case having the skill) are not supposed to be able to be deleted. So trying to remove bullseye routing in your case will throw that error.
Thanks,
Fergal
------------------------------
Fergal McLaughlin
Software Engineer Intern
Original Message:
Sent: 04-04-2025 09:07
From: William Valin
Subject: [BUG?] Error when removing Bullseye routing
Thank you! I'll be having a look here on in a while to see if there's any update.
------------------------------
William Valin
Original Message:
Sent: 04-04-2025 08:38
From: John Carnell
Subject: [BUG?] Error when removing Bullseye routing
#CXasCode
Hi William,
Thanks for posting this detailed description. I will open a ticket with DEVTOOLING team to investigate. I can't give an ETA on it, but I will make sure they respond to the post once they start.
Thanks,
John
------------------------------
John Carnell
Director, Developer Engagement
Original Message:
Sent: 04-03-2025 10:17
From: William Valin
Subject: [BUG?] Error when removing Bullseye routing
Hello everyone hope you're having a nice day.
Our team is currently having issues with the Bullseye routing and we're looking for help. Given this queue test_bullseye_routing_queue for which we activated the Bullseye routing:
We now wish to remove the Bullseye routing and the API returns this error:
Error: Failed to update queue test_bullseye_routing_queue error: API Error: 400 - Queue bullseye ring 3 has members and cannot be removed. (0076c4a5-1883-4190-be3e-369fa3ebb865)││ with genesyscloud_routing_queue.test_bullseye_routing_queue,│ on division_test.tf.json line 6, in resource.genesyscloud_routing_queue.test_bullseye_routing_queue:│ 6: }││ {"resourceType":"genesyscloud_routing_queue","method":"PUT","path":"/api/v2/routing/queues/57e78f33-6571-43be-957f-0b44140a023a","statusCode":400,"errorMessage":"API│ Error: 400 - Queue bullseye ring 3 has members and cannot be removed.│ (0076c4a5-1883-4190-be3e-369fa3ebb865)","correlationId":"0076c4a5-1883-4190-be3e-369fa3ebb865"}
The problem is that a user has the associated skill skill_bullseye_testing, which is part of the bullseye_testing skill group, and it blocks the deletion of the member from happening.
This is the terraform we used. Removing the bullseye_rings out of the queue will reproduce the issue as long as a user is associated to the skill_bullseye_testing above 1 star:
{ "resource": { "genesyscloud_routing_queue": { "test_bullseye_routing_queue": { "name": "test_bullseye_routing_queue", "bullseye_rings": [ { "expansion_timeout_seconds": 2, "member_groups": { "member_group_id": "${genesyscloud_routing_skill_group.skillgroup_test_languagesetter.id}", "member_group_type": "SKILLGROUP" } }, { "expansion_timeout_seconds": 120, "member_groups": { "member_group_id": "${genesyscloud_routing_skill_group.skillgroup_bullseye_testing.id}", "member_group_type": "SKILLGROUP" } } ] } }, "genesyscloud_routing_skill_group": { "skillgroup_test_languagesetter": { "description": "Generated for testing", "name": "test_LanguageSetter" }, "skillgroup_bullseye_testing": { "description": "Generated for testing", "name": "bullseye_testing", "division_id": "${genesyscloud_auth_division.division_test_bullseye.id}", "skill_conditions": "[{\"languageSkillConditions\": [], \"operation\": \"And\", \"routingSkillConditions\": [{\"childConditions\": [], \"comparator\": \"GreaterThanOrEqualTo\", \"proficiency\": 1, \"routingSkill\": \"skill_bullseye_testing\"}]}]" } }, "genesyscloud_routing_skill": { "skill_bullseye_testing": { "name": "skill_bullseye_testing" } }, "genesyscloud_auth_division": { "division_test_bullseye": { "description": "Test Bullseye", "home": false, "name": "DIVISION_TEST_BULLSEYE" } } }}
#Uncategorized
------------------------------
William Valin
------------------------------