jon.vansteen Genesys Employee
November 21

Hi @Rohit.Sharma3,

Sorry for the delay. Is this moving a flow between different organizations? Could you try removing the usages of

length:
  noValue: true

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


Visit Topic to respond.


Previous Replies

Rohit.Sharma3
November 14

Hi Jon,

Send you configuration on direct message.

Regards,
Rohit

jon.vansteen Genesys Employee
November 14

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
November 13

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" {
    • file_content_hash = "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.genesyscloud_flow.testobject: Still creating... [10s elapsed]
module.flow-inboundcall.genesyscloud_flow.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":"genesyscloud_flow","method":"GET","path":"/api/v2/flows/jobs/xxxxxxxxxxxxxxxxxx","statusCode":200,"correlationId":"xxxxxxxxxxxxxx"}
on modules/flow/inboundcall/testobject.tf line 1, in resource "genesyscloud_flow" "testobject":
1: resource "genesyscloud_flow" "testobject" {

Can you please check what can be the issue?

Regards,
Rohit S


Visit Topic to respond.

You are receiving this because you enabled mailing list mode.

To unsubscribe from these emails, click here.