Just noticed that the data action fails to deploy via CLI with a 400 error when using nested objects. The JSON validates locally but the API rejects the structure.
- region: au-1
- gc-cli: v1.28.0
- command:
genesys cloud integrations data-action create --file action.json
Error response indicates Invalid property path. Is there a limitation on nested depth for this endpoint?