Architect flow failing on digital channel mapping after zendesk migration

Having some config trouble here… i am migrating our support workflows from zendesk to genesys cloud and hitting a wall with the architect flow. in zendesk, we used to route tickets based on tags and priority fields directly. now, i am trying to replicate that logic using the ‘set interaction attributes’ block in architect, but the flow fails immediately after the first decision block.

the error log shows a 400 bad request on the /api/v2/architect/flows endpoint when i try to save the flow. the specific error message is ‘invalid attribute type for digital channel context’. i am using the sdk version 1.0.5 for the integration. i have mapped the zendesk ticket priority to a custom attribute in genesys, but it seems like the system expects a different data format. is there a specific way to handle the ticket-to-interaction mapping for digital channels? i need to preserve the priority logic we had in zendesk. any help would be appreciated.

Make sure you validate the interaction attribute schema before saving.

Cause: The 400 error indicates the payload contains attribute definitions that do not match the pre-registered Interaction Attribute Schema in Genesys Cloud.

Solution: Define the custom attributes in the Admin > Interaction Attributes section first, then reference those exact IDs in the Architect ‘Set Interaction Attributes’ block.

Check your attribute types before pushing the flow.

1. Verify the schema in Admin matches the payload exactly.
2. Save and publish the schema first.
3. Retry the API call.