Hi Borys Spiridonov,
Apologies for the hassle here.
The provider is updated to make sure it is consistent with the UI / API here.
The UI/API doesn't allow you to have less than 2 bulls eye rings. As shown in UI screen below , the final ring in the UI is displayed as "route to all agents in queue", and there are no actions associated with it.

The API throws an error too if queue with 1 bullseye ring is tried to be created.
{
"message": "Bullseye must have at least two rings.",
"code": "bad.request",
"status": 400,
"messageWithParams": "Bullseye must have at least two rings.",
"messageParams": {},
"contextId": "1cef5625-47c7-429d-a874-1496bd1cbc05",
"details": [],
"errors": []
}
In order to over come the problem you mentioned, We would suggest you to add a new bullseye like below for the queue configuration in terraform.
bullseye_rings {
expansion_timeout_seconds = 5
}
Meanwhile I will talk with the API and UI team to be more clear in the UI about number of bullseyes or if there is a story to remove the final ring completely in the future. As no actions can be associated with it.
Hope this helps.
Thanks
Hemanth
------------------------------
Hemanth Dogiparthi
Manager, Software Engineering
------------------------------
Original Message:
Sent: 12-04-2025 05:52
From: Borys Spiridonov
Subject: Terraform provider error: Attribute bullseye_rings requires 2 item minimum, but config has only 1 declared.
Hi,
We attempted to update the Genesys Terraform provider from 1.68.6 to 1.72.2 and are facing the following constraint:
Error: Not enough list itemswith module.queues.genesyscloud_routing_queue.SAFETY_TIER1_ESC_CHINA_ALL_LANGUAGES_GLOBAL_EMAIL_XFER_PAR_Qon queues/V1_QUEUES_Part_5.tf line 1425, in resource "genesyscloud_routing_queue" "SAFETY_TIER1_ESC_CHINA_ALL_LANGUAGES_GLOBAL_EMAIL_XFER_PAR_Q":resource "genesyscloud_routing_queue" "SAFETY_TIER1_ESC_CHINA_ALL_LANGUAGES_GLOBAL_EMAIL_XFER_PAR_Q" {Attribute bullseye_rings requires 2 item minimum, but config has only 1 declared.
It appears the recent provider version introduces a constraint on bullseye routing configuration, requiring at least two rings.
Our company is using bullseye routing with a single ring on 100s of queues, so this puts us in the situation where we cannot update the Terraform provider.
1. Genesys UI allows configuring the queue with a single ring in the bullseye config. So could you please explain what's happening with the Terraform provider?
2. How to work around this and preserve our queue configuration?
#PlatformAPI
------------------------------
Borys Spiridonov
.
------------------------------