DEPLOY_PIPELINE failing - TRANSFER_BLOCK SCHEMA_VERSION mismatch!

Hi all! We’re running into a really weird issue with our DEPLOY_PIPELINE - it’s failing when we try to update an IVR flow. It’s super frustrating, but I think we can figure it out together! :sweat_smile:

The error we’re getting is a 400 BAD_REQUEST - the validator is complaining about the SCHEMA_VERSION in the TRANSFER_BLOCK of the IVR. We’re using the Zoom Contact Center SDK for Node.js - version 2.1.3, and pushing the flow definition through a custom DEPLOY_PIPELINE.

It seems the SDK is stripping the FLOW_VERSION when it prepares the payload for the API. This is happening even though we’re explicitly setting it in the TRANSFER_BLOCK configuration. I’ve checked the IVR DEFINITION and the FLOW_VERSION is set correctly there, but it’s not making its way into the API call!

Here’s the error payload we’re getting back from the API:

{
 "errors": [
 {
 "code": "invalid_schema",
 "message": "Schema validation failed for TRANSFER_BLOCK. Missing required property: SCHEMA_VERSION",
 "field": "transferBlock.schemaVersion"
 }
 ],
 "requestId": "some-unique-id"
}

We’ve confirmed the TRANSFER_BLOCK itself is valid otherwise - it’s just missing this SCHEMA_VERSION. Any thoughts on how to prevent the SDK from stripping this? I’ve tried adjusting the DEPLOY_PIPELINE to include it manually but no luck so far. The ROUTING configuration is correct. It’s definitely a pipeline issue.

Three coffees. Schema version mismatch usually means the flow definition in the pipeline doesn’t match what’s actually deployed - try a GET on /api/v2/flows/{\flowId}and compare theTRANSFER_BLOCK` schema version to what’s in your pipeline JSON. Is it a simple redeploy issue, or are you updating the flow mid-pipeline?