Can anyone clarify the expected payload structure for the conditional block within the Architect flow API? We are attempting to programmatically update a flow via PUT /api/v2/architect/flows/{flowId} but consistently receiving a 400 Bad Request when including specific attribute checks.
The error response indicates: {"message": "Invalid condition definition", "code": "invalid_condition"}. The documentation suggests that the condition object requires a type of attribute and a value object, yet our payload includes all required fields:
{
"type": "attribute",
"value": {
"id": "interaction.attributes.custom.priority",
"operator": "eq",
"value": "high"
}
}
We have verified that the interaction attribute schema is registered in the organization. The issue appears to be specific to the nested object structure rather than a missing attribute. Is there a known limitation regarding deeply nested attribute paths in the conditional logic schema? We are using the latest OpenAPI spec version but suspect a discrepancy between the documented schema and the actual validation logic enforced by the Genesys Cloud backend.