ManjuR | 2025-02-27 22:33:25 UTC | #1
Hi team,
We are testing our CICD pipeline to sync data in Genesys Cloud Orgs.
Today we are getting the following error for all 133 queues configured on our env.
The pipeline was successful y'day and today it got failed.
We could see there is a new version 1.59.0 released today.
Is this issue happening because of this release 1.59.0? Please can you check.*
<strong>╷ │ Error: Failed to update queue ABBOSBillingQ error: API Error: 400 - Value [] is not valid for field type [Mode]. Allowable values are: AgentFirst, CustomerFirst (d93ad2a9-fbe5-4a62-8496-a591305b34e6) │ │ with genesyscloudroutingqueue.ABBOSBillingQ, │ on queues.tf.json line 229, in resource.genesyscloudroutingqueue.ABBOSBillingQ: │ 229: }, │ │ {"resourceType":"genesyscloudrouting_queue","method":"PUT","path":"/api/v2/routing/queues/87945aa5-b20e-4f98-899f-801263401cf2","statusCode":400,"errorMessage":"API │ Error: 400 - Value [] is not valid for field type [Mode]. Allowable values │ are: AgentFirst, CustomerFirst │ (d93ad2a9-fbe5-4a62-8496-a591305b34e6)","correlationId":"d93ad2a9-fbe5-4a62-8496-a591305b34e6"} ╵ ╷</strong>
Regards, Manju
John_Carnell | 2025-02-27 22:40:17 UTC | #2
Hi Manju,
Do you lock your terraform provider to a specific version and just upgraded or do you always pull the latest provider (which I would not recommend). If you have not updated your terraform provider and are locked into an earlier version, then this sudden change could indicate a version change. We will need to reach out to the API team because something in the backend API will have changed.
Thanks, John Carnell Direcror, Developer Engagmenet
ManjuR | 2025-02-28 02:07:26 UTC | #3
hi John,
Earlier we were specific terraform provider version and then upgraded to 1.56.1. In that release we faced " │ Error: [{0 prompt file not transcoded. User prompt ID:" issue and got an update stating that the issue will be fixed as of v1.58.0.
When v1.58.0 was released, we updated the code to pull latest provider and faced this issue. We will revert to (n-1) version.
Regards, Manju
John_Carnell | 2025-02-28 13:44:27 UTC | #4
Hi Manju,
Thanks for the information. I have a high-priority ticket with our DevTooling team and hope to have more information today.
John_Carnell | 2025-02-28 15:46:30 UTC | #5
Hi Manju,
We have identified the bug as a bug in the provider and will be releasing a point release today or Monday with a fix.
Hemanth | 2025-03-03 13:29:54 UTC | #6
Hi @ManjuR please use version v1.59.1 . The issue is fixed in this release.
ManjuR | 2025-03-03 14:27:46 UTC | #7
With the latest release we validated, the issue has been resolved
Thanks John and Hemanth !!!
Regards, Manju
system | 2025-04-02 14:28:17 UTC | #8
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 31957