Rohit.Sharma3 | 2024-11-13 18:18:00 UTC | #1
Hi Team, We are facing a issue while committing flow to Genesys Cloud with "the property length is not writable" Error. We have upgraded system from v1.44.0 to v1.52.0 to check if issue is resolved in latest version, but issue persists in latest version as well. Following is the deploy logs:
module.flow-inboundcall.genesyscloud_flow.testobject will be created
- resource "genesyscloud_flow" "testobject" {
- filecontenthash = "xxxxxx----hash------xxxxxx"
- filepath = "modules/flow/inboundcall/testobject.yaml"
- id = (known after apply)
}
Plan: 1 to add, 0 to change, 0 to destroy.
module.flow-inboundcall.genesyscloudflow.testobject: Still creating... [10s elapsed] module.flow-inboundcall.genesyscloudflow.testobject: Still creating... [20s elapsed]
Warning: Applied changes may be incomplete
The plan was created with the -target option in effect, so some changes requested in the configuration may have been ignored and the output values may not be fully updated. Run the following command to verify that no other changes are pending: terraform plan
Note that the -target option is not suitable for routine use, and is provided only for exceptional situations such as recovering from errors or mistakes, or when Terraform specifically suggests to use it as part of an error message.
Error: flow publish failed. JobID: jobxxxx-id-xxxx, tracing messages: setting the Archy exit code to 100
the property length is not writable.
error(s) encountered
exit code: 100 {"resourceName":"genesyscloudflow","method":"GET","path":"/api/v2/flows/jobs/xxxxxxxxxxxxxxxxxx","statusCode":200,"correlationId":"xxxxxxxxxxxxxx"} on modules/flow/inboundcall/testobject.tf line 1, in resource "genesyscloudflow" "testobject": 1: resource "genesyscloud_flow" "testobject" {
Can you please check what can be the issue?
Regards, Rohit S
jon.vansteen | 2024-11-14 13:16:58 UTC | #2
Hi @Rohit.Sharma3,
Could you please send me the yaml file you are using for this in a direct message? That will help to figure out what is going on.
Thanks, Jon
Rohit.Sharma3 | 2024-11-14 20:11:31 UTC | #3
Hi Jon,
Send you configuration on direct message.
Regards, Rohit
jon.vansteen | 2024-11-21 18:37:43 UTC | #4
Hi @Rohit.Sharma3,
Sorry for the delay. Is this moving a flow between different organizations? Could you try removing the usages of
from your yaml file for the Nuance Mix bots?
If this works (and you are moving between different organizations) I wonder if there is a configuration mismatch between the environments for the Nuance Mix bot.
Let me know!
Thanks, Jon
Rohit.Sharma3 | 2024-11-21 23:16:29 UTC | #5
Thank you Jon, We will test it after removing usage and try it.
Regards, Rohit
sidd3443 | 2024-11-25 17:03:24 UTC | #6
Hey Jon,
We have built the flow using Genesys Architect UI and trying to publish this flow (yaml) using CICD (Archy) and we are calling the Nuance Mix Bots from the Genesys Architect Flow. And to answer your question, no we are not moving this flow to a different organization and trying to publish the yaml in same organization. length : noValue : true is a Nuance Data Type and how can we skip this Data Type as this appears by Default when we call the published nuance bot.
jon.vansteen | 2024-11-26 21:51:03 UTC | #7
Hi @sidd3443,
Just curious, did the publish then work when you removed the length property from the YAML? That would help in answering your other questions.
Thanks, Jon
system | 2024-12-26 21:51:03 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: 30368