Error Codes

Flow Management API Error Codes

When managing (creating, updating, deleting, or publishing) your Flows, you may run into the occasional error. The following table outlines the different error codes you might see, and what you can do to fix the problem. Don’t see your error code listed below? Check out this list of Cloud API error codes.

Error Code	Description	Possible Solutions
100	Flow name is not unique	You may be trying to create a Flow with a name already used by another Flow on the same WhatsApp Business Account. Flow name should be unique within one WhatsApp Business Account. Confirm that you’re creating the Flow on the correct account or use a different name for your Flow. See Creating a Flow for more information.
	Invalid Flow JSON version	The Flow JSON version you specified in your API call isn’t valid. Verify there isn’t a mistake with version sent (e.g., a typo or leaving it blank). If the version looks correct, it may be expired and you’ll need to upgrade to a later version. For the latest active versions see the Changelog. For more details on how versioning works for WhatsApp Flows, see the Versioning reference.
	Invalid Flow JSON `data_api_version`	The Data API version you specified in your API call isn’t valid. Verify there isn’t a mistake with version sent (e.g., a typo or leaving it blank). If the version looks correct, it may be expired and you’ll need to upgrade to a later version. For the latest active versions see the Changelog. For more details on how versioning works for WhatsApp Flows, see the Versioning reference.
	Flow with specified ID does not exist	The Flow ID you provided was not found in your account. Confirm that the ID provided is correct and verify that you have access it with the credentials provided.
	Only one clone source can be set	You provided values for both `clone_flow_id` and`clone_template`. When cloning a Flow, you can only provide one of these fields. Unset one of them and try your request again.
	Specify Endpoint Uri in Flow JSON	You provided `endpoint_uri` and `clone_flow_id` which corresponds to a Flow with Flow JSON version below 3.0. For Flow JSON versions below 3.0 `endpoint_uri` should be specified as `data_channel_uri` property in the Flow JSON. Do not specify `endpoint_uri` param when cloning a Flow with Flow JSON version below 3.0. See API reference for details.
	Invalid Endpoint URI	Provide a valid URL.
139000	Blocked By Integrity	Unfortunately we’ve identified an issue with integrity in your account and have prevented you from creating or publishing your Flow. To get this issue resolved for your account, get in touch with us via the Support.
139001	Flow can’t be updated	You attempted to update a Flow that has already been published. Once published, Flows can no longer be updated (see Flows Status Lifecycle). To update a published Flow, you’ll have to clone the Flow (see Creating a Flow) and republish the new Flow. Once published, you can start sending the newly modified Flow instead of the existing one.
	Error while processing Flow JSON	Due to an internal error, the Flow JSON was saved but internal processing failed (which may prevent the Flow from serving properly). First, retry the exact same request as the issue may be transient. If retrying results in the same error again, contact us via the support to help get the error resolved.
	Specify Endpoint Uri in Flow JSON	You provided `endpoint_uri` param for a Flow with Flow JSON version below 3.0. For Flow JSON versions below 3.0 `endpoint_uri` should be specified as `data_channel_uri` property in the Flow JSON. Do not specify `endpoint_uri` param when updating a Flow with Flow JSON version below 3.0. See API reference for details.
139002	Publishing Flow in invalid state	You tried to publish a Flow that isn’t a draft. Once a Flow leaves the draft state, they cannot be republished (see Flows Status Lifecycle). If you need to modify a Flow that is no longer a draft, you’ll have to clone the Flow (see Creating a Flow) and republish the new Flow. Once published, you can start sending the newly modified Flow instead of the existing one.
	Publishing Flow with validation errorrs	You tried to publish a draft Flow that has validation errors. Flows with validation errors can be saved as a draft, but not published. Try viewing the Flow in the Flow Builder UI which will highlight and explain any errors (see Create Your First Flow for a guide to getting started with the Flows Builder UI. You can also view a list of validation errors for your Flow via the API (see Retrieving Flow Details). Once the errors are resolved, try publishing your Flow again.
	Publishing Flow without `data_channel_uri`	You need to set the “data_channel_uri” property before you can send or publish a flow.
	Publishing without specifying `endpoint_uri` is forbidden	Please set `endpoint_uri` property for a Flow before publishing. Starting from Flow JSON version 3.0 `endpoint_uri` should be specified via API. See API reference for details.
	Versions in Flow JSON file are not available for publishing	The flow is using an unsupported version. You can check the list of currently available versions in the changelog.
	No Phone Number connected to WhatsApp Business Account	You need to add a phone number to your WhatsApp Business Account before you can send or publish a flow.
	Missing Flows Signed Public Key	You need to upload and sign a public key to a phone number before you can send or publish a flow.
	No Application Connected to the Flow	You need to connect a Meta app to the flow before you can publish it.
	Endpoint Not Available	You need to verify that the endpoint is available and that you’ve implemented a health check before publishing.
	WhatsApp Business Account is not subscribed to Flows Webhooks	You need to verify that your WhatsApp Business account is subscribed to Flows webhooks.
139003	Can’t deprecate unpublished flow	You attempted to deprecate a Flow that hasn’t yet been published. Deprecating a Flow is only permitted after it’s been published (see Deprecating a Flow). For Flows that are still drafts, you should delete any Flows you no longer need (see Deleting a Flow).
	Flow is already deprecated	You tried to deprecate a Flow that is already marked as deprecated. You may ignore this error as your target state (the Flow being deprecated) has already been achieved.
139004	Can’t delete published Flow	After a Flow has been published, it cannot be deleted. Please deprecate instead.
139006	Metrics threshold is not reached	Not enough data to provide flow metrics

Business Endpoint Error Codes

If the Flow is using a business-provided endpoint, that endpoint may return specific HTTP response codes in case of certain types of errors to trigger appropriate client-side behavior.

HTTP Response Code	Server-side situation	Client-side behavior and details
421	The payload cannot be decrypted	The WhatsApp client will re-fetch a public key and re-send the request. If the request fails, a generic error will be shown on the client. See Implementing Endpoints for Flows for more details.
432	The request signature authentication fails	A generic error will be shown on the client.
427	The Flow token is no longer valid	A generic error will be shown on the client, and the CTA button will be disabled for the user. You can send a new message to the user generating a new Flow token. This action may be used to prevent users from initiating the same Flow again. You are able to set an error message to display to the user. For example: `json<br />HTTP/2 427<br />content-type: application/json<br />content-length: 51<br />date: Wed, 06 Jul 2022 14:03:03 GMT<br />{“error_msg”: “The order has already been placed”}<br />` See Implementing Endpoints for Flows for more details.

On-Premise WhatsApp Business API Client Error Codes

Flow specific error codes returned by On-Premise Client. For the full list of On-Premise error codes see this page.

Error Code	Description
`2064` - Invalid Flow ID	Flow with specified ID does not exist or does not belong to your WhatsApp Business Account (WABA), or it is in invalid state.
`2065` - Invalid Flow Message Version	Flow message Version is invalid. See currently supported message version in Flows Changelog
`2066` - Invalid Flow Mode	Returned when Flow in `DRAFT` state is sent with specifying draft mode or `PUBLISHED` Flow is sent with draft mode.
`2067` - Flow DRAFT Mode Not Allowed	Unable to send `DRAFT` Flow, please check status page for any ongoing issues and if problem persists please contact support.
`2068` - Flow is blocked	Flow is in blocked state. This error may also be returned if flow uses an endpoint and required setup is incomplete, e.g. public key is not uploaded or became invalid. See Implementing Endpoint for Flows.
`2069` - Flow is throttled	Flow is in throttled state and 10 messages using this flow were already sent in the last hour.
`2070` - Invalid Flow Version	Flow version is invalid or expired. See currently supported versions in Flows Changelog

Cloud API Error Codes

Flow specific error codes returned by Cloud API. For the full list of Cloud API error codes see this page.

Code	Description	Possible Solutions	HTTP Status Code
`132068` Flow is blocked	Flow is in blocked state.	Correct the Flow	`400` Bad Request
`132069` Flow is throttled	Flow is in throttled state and 10 messages using this flow were already sent in the last hour.	Correct the Flow	`400` Bad Request

Error Types Reported via WebHook Alerts or Propagated Back to Endpoint

These error codes might be sent through business endpoint from client devices or be included in webhook alert payload.

Code	Description	Possible Solutions
`timeout_error`	Endpoint request has timed out. It took more than 10 seconds to process the endpoint request.	Improve the endpoint performance so it can process requests in less than 10 seconds.
`missing_capability`	The app linked to Flow does not have required endpoint capability
`cannot_be_served`	The Flow message cannot be sent and opened by recipients.	Flow is not in `DRAFT` or `PUBLISHED` state. Other common problems: - WABA is blocked by Integrity. Check the Business account page for any quality issues. - The `version` or `data_api_version` properties are missing in Flow JSON. Add these properties to the Flow JSON file
`no_http_response_error`	Endpoint request connection closed without receiving valid http response.	Ensure that the endpoint always returns a valid response in the correct format.
`unexpected_http_status_code`	The endpoint response had unexpected status code (eg. `500`)	Ensure that the endpoint response always has expected status code.
`public-key-missing`	The client was not able to retrieve the business’s public key from WA servers.	Make sure that the correct flow public key is uploaded for the phone number from which you are sending flows. If a problem persists contact support.
`public-key-signiture-verification`	The client was not able to verify the signature of the business’s public key.	Make sure that the correct flow public key with signature is uploaded for the phone number from which you are sending flows. If you re-installed on-prem client recently please make sure you re-upload public key with updated signature. If a problem persists contact support.
`response-decryption-error`	The client failed to decrypt the payload sent by the business.	Verify that the same key is uploaded for the phone number and is also being used to encrypt endpoint payloads. If a problem persists contact support.
`invalid-screen-transition`	The client received the next screen which is not matching the routing model expressed in flow JSON layout.	Next screen navigation needs to match what’s expressed in the routing model of the flow layout. If the routing model needs to be updated for a published flow, the flow needs to be cloned, edited and published again.
`payload-schema-error`	The client received the screen data which are not conforming to screen data schema defined in flow JSON layout.	Make sure the screen data sent for each screen complies with the schema defined in the flow JSON layout.
`business-decryption-error`	The client received the 421 error code from the business even after refreshing the public key.	Re-upload the Flow’s public key and try again.

Static Validation Errors

The following tables detail the static validation errors that may be returned while developing Flow JSON.

Schema Validation Errors

Error Code	Error Message	Details	Sample Flow JSON
`INVALID_PROPERTY_KEY`	Property (propertyName) cannot be specified at (errorPath). When inside a component: Property (propertyName) cannot be specified at (componentName) on (errorPath).	Additional properties are not allowed in Flow JSON. See here for all allowed properties in Flow JSON.	`json<br />{<br /> "version": "2.1",<br /> "myNewProp": "hello"<br /> ...<br />}<br />`
`INVALID_PROPERTY_VALUE`	Invalid value found for property (propertyName) at (errorPath).	See here for all allowed property values in Flow JSON.	`json<br />{<br /> ...<br /> "layout": "myNewLayout"<br />}<br />` `json<br />{<br /> ...<br /> "layout": {<br /> "type": "SingleColumnLayout",<br /> "children": [<br /> {<br /> "type": "newComponent"<br /> ...<br /> }<br /> ]<br />}<br />`
`INVALID_PROPERTY_TYPE`	Expected property (errorPath) to be of type (expectedType), but found (actualType).	Invalid type of value found for a valid property type. See here for all expected types of each property in Flow JSON.	`json<br />{<br /> "type": "TextArea",<br /> "label": "Your input",<br /> "enabled": "yes"<br />}<br />`
`INVALID_PROPERTY_VALUE_FORMAT`	Property ' ${propertyName}' should be in '$ ' format.	For example, property data_channel_uri must be in uri format.	`json<br />{<br /> "version": "2.1",<br /> "data_channel_uri": "placeholder_uri",<br /> "screens": [<br /> ...<br /> ]<br />}<br />`
MIN_ITEMS_REQUIRED``MIN_CHARS_REQUIRED	Property ' ${propertyName}' should have at least '$ ' $.	Attributes that must have minimum items or characters. For example, screen id must have a minimum length of 1. The Screens array should have at least 1 item.	`json<br />{<br /> "screens": [<br /> {<br /> "id": "",<br /> }<br /> ]<br />}<br />` `json<br />{<br /> "version": "2.1",<br /> "screens": []<br />}<br />`
`MISSING_REQUIRED_TYPE_PROPERTY`	Required property ’$’ is missing.	Attributes that must exist. For example, “ type” of a component must be specified.	`json<br />{<br /> "screens": [<br /> {<br /> "id": "FIRST",<br /> "layout": {<br /> "children": [<br /> {<br /> "text": "Description",<br /> }<br /> ]<br /> }<br /> }<br /> ]<br />}<br />`
`PATTERN_MISMATCH`	Property (propertyName) should only consist of alphabets and underscores. Property (propertyName) should be of type ‘(type)’ or have dynamic data format of the form ${screen.data.your_value} or$ . Property (propertyName) should have dynamic data format of the form $. Property (propertyName) should not be blank or empty string. Property (propertyName) should match the pattern ‘(pattern)’.	Certain attributes must be in a specified format. For example, a screen name can only contain alphabets and underscores. Property ‘max-chars’ in TextInput must be a number or a string of the form “$.	`json<br />{<br /> "screens": [<br /> {<br /> "id": "FIRST_1",<br /> "layout": {<br /> "children": [<br /> {<br /> "type": "TextInput",<br /> "name": "Description",<br /> "label": "Enter decsription",<br /> "max-chars": "Hundred"<br /> }<br /> ]<br /> }<br /> }<br /> ]<br />}<br />`
`INVALID_ENUM_VALUE`	Value should be one of: [$]. Example, Value should be one of: [data_exchange, navigate].	Value can only be one of the allowed values. For example, Action complete can only be specified on Footer.	`json<br />{<br /> "screens": [<br /> {<br /> "id": "FIRST_SCREEN",<br /> "layout": {<br /> "children": [<br /> {<br /> "type": "EmbeddedLink",<br /> "text": "link",<br /> "on-click-action": {<br /> "name": "complete",<br /> "payload": {}<br /> }<br /> }<br /> ]<br /> }<br /> }<br /> ]<br />}<br />`
`INVALID_DEPENDENCIES`	Footer should have property left-caption when property right-caption is present.	Indicates the dependency of a property to exist based on another property. For example, if ‘ left-caption’ is specified at Footer then ‘ right-caption’ must be specified as well.	`json<br />{<br /> "screens": [<br /> {<br /> "id": "FIRST_SCREEN",<br /> "layout": {<br /> "children": [<br /> {<br /> "type": "Footer",<br /> "left-caption": "left",<br /> "on-click-action": {<br /> "name": "complete",<br /> "payload": {}<br /> }<br /> }<br /> ]<br /> }<br /> }<br /> ]<br />}<br />`
`NOT_KEYWORD_SCHEMA_VALIDATION_FAILED`	Properties ‘(propertyName)’ and [(not_required_properties)] must be present exclusively at (componentName). Properties [(not_required_properties)] must be present exclusively at (componentName). Property ‘success’ can only be specified on a terminal screen. The NOT keyword schema validation failed. Please refer to the Flow JSON schema.	Indicates the properties which cannot exist together in the Flow JSON component. For example, only one of ‘ center-caption’ and [‘ left-caption’ or ‘ right-caption’] can be specified at Footer. Or Property ‘success’ is specified on a non-terminal screen.	`json<br />{<br /> "screens": [<br /> {<br /> "id": "FIRST_SCREEN",<br /> "layout": {<br /> "children": [<br /> {<br /> "type": "Footer",<br /> "left-caption": "left",<br /> "center-caption": "center",<br /> "on-click-action": {<br /> "name": "complete",<br /> "payloadx": {}<br /> }<br /> }<br /> ]<br /> }<br /> }<br /> ]<br />}<br />` `json<br />{<br /> "version": "2.1",<br /> "screens": [<br /> {<br /> "terminal": "false",<br /> "success": "true",<br /> ... <br /> }<br /> ]<br /> }<br />`
`INVALID_PROPERTY_VALUE`	At least one terminal screen must have property ‘success’ set as true.	This property marks whether terminating on a terminal screen should be considered a successful business outcome. More info .	`json<br /> "version": "2.1",<br /> "screens": [<br /> {<br /> "terminal": "true",<br /> "success": "false",<br /> ... <br /> }<br /> ]<br />}<br />`
`INVALID_FLOW_JSON`	Flow JSON is not valid.	There can be multiple reasons for an invalid Flow JSON. For example, there may be an unnecessary trailing comma. Exact location of these errors is hard to point out since an invalid JSON cannot be parsed.	`json<br />{<br /> "routing_model": {},<br /> "screens": [<br /> ...<br /> ],,<br />}<br />`
`INVALID_FLOW_JSON`	No schema found for the given version (version). Invalid schema found for the given version $.	Either the Flow JSON version is not valid or there is an internal error.
`INVALID_PROPERTY_KEY`	Property `data_api_version` is no longer supported in Flow JSON as of version ‘3.0’. Please configure your endpoint URI using Flows API or Builder. Refer Flows documentation at ‘/docs/whatsapp/flows‘ for more information.	Property `data_api_version` cannot be specified inside the Flow JSON starting from version 3.0.	`json<br />{<br /> "version": "3.0",<br /> "data_api_version": "3.0",<br /> "screens": [<br /> ...<br /> ],<br />}<br />`
`KEYWORD_ONE_OF`	Property ‘(propertyName)’ must be defined inside parent property ‘Form’.	Before version 4.0, form components can only be defined inside a parent Form component. Starting from version 4.0, Forms are optional.	json<br />{<br /> "version": "2.1",<br /> "screens": [<br /> {<br /> "layout": {<br /> "type": "SingleColumnLayout",<br /> "children": [<br /> {<br /> "type": "TextInput",<br /> "name": "path2",<br /> "label": "Path"<br /> },<br /> {<br /> "type": "Form",<br /> "name": "flow_path",<br /> "children": [<br /> {<br /> "type": "TextInput",<br /> "name": "path",<br /> "label": "Path"<br /> },<br /> ...<br /> }<br /> ]<br /> }<br /> }<br />}<br />	\
\

FLow JSON Version Errors\

| Error Code | Error Message | Details | Sample Flow JSON | \ | | ---------- | ------------- | ------- | ---------------- |
| INVALID_FLOW_JSON_VERSION | Invalid Flow JSON version. | | json { "version": "2024.0", ... }  |
| MISSING_FLOW_JSON_VERSION | Flow JSON version is not specified. | Specifying the Flow JSON version is necessary. |

json&lt;br /&gt;&#123;<br />        "data_api_version": "3.0",<br />        "screens": [<br />          ...<br />        ]<br />&#125;&lt;br /&gt;

json&lt;br /&gt;&#123;<br />        "version": 100,<br />        "screens": [<br />          ...<br />        ]<br />&#125;&lt;br /&gt;

|
| UNAVAILABLE_FLOW_JSON_VERSION | The Flow JSON version is not available for your WABA ID. | Some versions are enabled only for Beta users and may not be enabled for public use. |

json&lt;br /&gt;&#123;<br />        "version": "A.B",<br />        "screens": [<br />          ...<br />        ]<br />&#125;&lt;br /&gt;

|
| NO_SUPPORTED_DATA_API_VERSION | No supported Data API version found for given Flow JSON version. | Data api version is required for data_exchange action.
This error should ideally never be shown in production flows if the Flow JSON version is valid. |

json&lt;br /&gt;&#123;<br />        "version": "A.B",<br />        "data_api_version": "C.D",<br />        "screens": [<br />          ...<br />        ]<br />&#125;&lt;br /&gt;

|
\

Routing Model Errors\

| Error Code | Error Message | Details | Sample Flow JSON | \ | | ---------- | ------------- | ------- | ---------------- |
| INVALID_ROUTING_MODEL | Following screens are missing in the routing model: (screenIDs). | In data channel flow json, when screen is not present in routing_model |

json&lt;br /&gt;&#123;<br />        "routing_model": {"ABC":[]},<br />        "screens": [<br />            {<br />                "id": "FIRST_SCREEN",<br />...<br />

|
| INVALID_ROUTING_MODEL | Invalid screens found in the routing model: (screenIDs). | In data channel flow json, when source screen id of routing_model does not exist |

json&lt;br /&gt;&#123;<br />        "routing_model": {"ABC":[]},<br />        "screens": [<br />            {<br />                "id": "FIRST_SCREEN",<br />...<br />

|
| INVALID_ROUTING_MODEL | Following screens are not connected to any of the screens: (screenIDs). A connection is formed by the navigate screen action. | In data channel less flow json, when screen id not present in routing_model generated by actions data |

json&lt;br /&gt;&#123;<br />        "screens": [<br />            {<br />                "id": "FIRST_SCREEN",<br />                "layout": {<br />                    "children": [<br />                        {  "type": "Footer",                              <br />                            "on-click-action": {                                       <br />                            "name": "data_exchange",                                        <br />...<br />

|
| INVALID_ROUTING_MODEL | Following screens are not connected with the rest of the screens : (screenIDs). All screens should be connected. | In data channel flow json, when some screens can not be reached out starting from other screens |

json&lt;br /&gt;&#123;<br />        "routing_model": {<br />"FIRST_SCREEN":["SECOND_SCREEN"],<br />"THIRD_SCREEN":[]<br />},<br />...<br />

|
| INVALID_ROUTING_MODEL | Following screens are not connected with the rest of the screens via navigate screen action: (screenIDs). All screens should be connected. | In data channel less flow json, when some screens can not be reached out starting from other screens, via ‘navigate’ actions |

json&lt;br /&gt;&#123;<br />  "screens": [<br />    {<br />      "id": "FIRST_SCREEN",<br />      "layout": {<br />        "children": [<br />          {<br />            "type": "Footer",<br />            "on-click-action": {<br />              "name": "navigate",<br />              "next": {<br />                "name": "SECOND_SCREEN",<br />                "type": "screen"<br />              },<br />            }<br />          }<br />        ]<br />      }<br />    },<br />    {<br />      "id": "SECOND_SCREEN",<br />      ...<br />    },<br />    {<br />      "id": "THIRD_SCREEN",<br />      ...<br />    }<br />  ]<br />&#125;&lt;br /&gt;

|
| INVALID_ROUTING_MODEL | No entry screen found in the routing model. Expected a screen with no inbound edges as the entry screen. | In data channel flow json, when there is no entry screens, which do not have incoming screen |

json&lt;br /&gt;&#123;<br />  "screens": [<br />    {<br />      "id": "FIRST_SCREEN",<br />      "layout": {<br />        "children": [<br />          {<br />            "type": "Footer",<br />            "on-click-action": {<br />              "name": "navigate",<br />              "next": {<br />                "name": "SECOND_SCREEN",<br />                "type": "screen"<br />              },<br />            }<br />          }<br />        ]<br />      }<br />    },<br />    {<br />      "id": "SECOND_SCREEN",<br />      "layout": {<br />        "children": [<br />          {<br />            "type": "Footer",<br />            "on-click-action": {<br />              "name": "navigate",<br />              "next": {<br />                "name": "FIRST_SCREEN",<br />                "type": "screen"<br />              },<br />            }<br />          }<br />        ]<br />      },<br />      ...<br />    }<br />  ]<br />&#125;&lt;br /&gt;

|
| INVALID_ROUTING_MODEL | No entry screen found in the routing model. Add a screen that is not used as the next screen in any of the navigate actions. | In data channel less flow json when there is no entry screen i.e. a screen which does not have an incoming screen. |

json&lt;br /&gt;&#123;<br />        "routing_model": {<br />"FIRST_SCREEN":["SECOND_SCREEN"],<br />"SECOND_SCREEN":["FIRST_SCREEN"]<br />},<br />...<br />

|
| INVALID_ROUTING_MODEL | Loop detected in the routing model for screens: (screenIds). | In data channel flow json, when there is no loop between two screens. |

json&lt;br /&gt;&#123;<br />        "routing_model": {<br />"FIRST_SCREEN":["SECOND_SCREEN"],<br />"SECOND_SCREEN":["FIRST_SCREEN"]<br />},<br />...<br />

|
| INVALID_ROUTING_MODEL | Invalid screen found in the routing model: (screenId). | In data channel flow json, when a screen is not present in destinations in routing_model. |

json&lt;br /&gt;&#123;<br />  "routing_model": {"FIRST_SCREEN": []},<br />  "screens": [<br />    {<br />      "id": "FIRST_SCREEN",<br />      "terminal": true,<br />      ...<br />    },<br />    {<br />      "id": "SECOND_SCREEN",<br />      ...<br />    }<br />  ]<br />&#125;&lt;br /&gt;

|
| INVALID_ROUTING_MODEL | Number of branches exceeds the max limit of 10 for screen: (screenId). | In data channel flow json, a screen cannot have more than 10 outgoing screens. |

json&lt;br /&gt;&#123;<br />        "routing_model": {<br />"FIRST_SCREEN":["1", "2", "3", "4", "5", "6", "7", "8", "9", "10", "11", "12"],<br />...<br />},<br />...<br />

|
| INVALID_ROUTING_MODEL | Number of branches exceeds the max limit of 10 for screen: (screenId). Reduce navigate actions for the screen. | In data channel less flow json, when a screen has more than 10 outgoing screens calculated by ‘navigate’ actions |

json&lt;br /&gt;&#123;<br />  "screens": [<br />    {<br />      "id": "FIRST_SCREEN",<br />      "layout": {<br />        "children": [<br />          {<br />            "type": "Footer1",<br />            "on-click-action": {<br />              "name": "navigate",<br />              "next": {<br />                "type": "screen",<br />                "name": "1",<br />                ...<br />          },<br />          {<br />            "type": "Footer2",<br />            "on-click-action": {<br />              "name": "navigate",<br />              "next": {<br />                "type": "screen",<br />                "name": "2",<br />                ...<br />          }, <br />          ...  <br />          {<br />            "type": "Footer11",<br />            "on-click-action": {<br />              "name": "navigate",<br />              "next": {<br />                "type": "screen",<br />                "name": "11",<br />                ...<br />              },<br />          ...<br />  ]<br />&#125;&lt;br /&gt;

|
| INVALID_ROUTING_MODEL | Backward route [(destination)-)(source)] corresponding to forward route [(source)-)(destination)] is not allowed in the routing model. Only forward routes can be specified. | In data channel flow json, when there is a route from A -) B then B -) A. |

json&lt;br /&gt;&#123;<br />        "routing_model": {<br />"FIRST_SCREEN":["SECOND_SCREEN", ...],<br />"SECOND_SCREEN":["FIRST_SCREEN", ...]<br />},<br />...<br />

|
| INVALID_ROUTING_MODEL | Missing direct route from screen '

{source}' to screen '

' in the routing model, while it exists in the navigate screen action of screen ’$’. | In data channel flow json, when the routes formed by navigate actions are not present in the routing model supplied in the template |

json&lt;br /&gt;&#123;<br />  "version": "2.1",<br />  "routing_model": {"FIRST_SCREEN":[]},<br />  "screens": [<br />    {<br />      "id": "FIRST_SCREEN",<br />      "layout": {<br />        "children": [<br />          {<br />            "type": "Footer",<br />            "on-click-action": {<br />              "name": "navigate",<br />              "next": {<br />                "type": "screen",<br />                "name": "SECOND_SCREEN"<br />              },<br />              ...<br />    },<br />    {<br />      "id": "SECOND_SCREEN",<br />      ...<br />    }<br />  ]<br />&#125;&lt;br /&gt;

|
\

On-click Action Errors\

| Error Code | Error Message | Details | Sample Flow JSON | \ | | ---------- | ------------- | ------- | ---------------- |
| INVALID_ON_CLICK_ACTION_PAYLOAD | Missing Form component

&#123;expression&#125; for screen '

{screenId}’. | Form binding does not exist |

json&lt;br /&gt;&#123;<br />  "type": "Form",<br />  "name": "PASS_CUSTOM_VALUE",<br />  "children": [<br />    &#123;<br />      "type": "Footer",<br />      "on-click-action": &#123;<br />        "name": "complete",<br />        "payload": &#123;<br />          "input": "$&#123;form.not_present&#125;"<br />        &#125;<br />      &#125;<br />    &#125;<br />  ]<br />&#125;&lt;br /&gt;

|
| INVALID_ON_CLICK_ACTION_PAYLOAD | Missing dynamic data ‘

&#123;expression&#125;' in the data model for screen

{screenId}.
Missing dynamic data ‘

&#123;expression&#125;' in the screen data model. | Data binding does not exist | ```json&lt;br /&gt;&#123;<br /> "type": "Form",<br /> "name": "PASS_CUSTOM_VALUE",<br /> "children": [<br /> &#123;<br /> "type": "Footer",<br /> "on-click-action": &#123;<br /> "name": "complete",<br /> "payload": &#123;<br /> "input": "

{data.not_present}”
}
}
}
]
}

|\ | `INVALID_ON_CLICK_ACTION_PAYLOAD` | In the complete action payload, PhotoPicker can only be used if the value of the 'max-uploaded-photos' property doesn't exceed 1. | PhotoPicker’s 'max-uploaded-photos' property value has to be 1 to be used in top level of on-click-action payload |

json {
“children”: [
{
“type”: “PhotoPicker”,
“name”: “photo”,
“label”: “PASS_CUSTOM_VALUE”
},
{
“type”: “Footer”,
“label”: “PASS_CUSTOM_VALUE”,
“on-click-action”: {
“name”: “complete”,
“payload”: {
“photo”: ”${screen.FIRST_SCREEN.form.photo}”
}
}
}
]
}

|\ | `INVALID_ON_CLICK_ACTION_PAYLOAD` | In the complete action payload, DocumentPicker can only be used if the value of the 'max-uploaded-documents' property doesn't exceed 1. | DocumentPicker 'max-uploaded-documents' property value has to be 1 to be used in top level of on-click-action payload |

json {
“children”: [
{
“type”: “DocumentPicker”,
“name”: “doc”,
“label”: “PASS_CUSTOM_VALUE”
},
{
“type”: “Footer”,
“label”: “PASS_CUSTOM_VALUE”,
“on-click-action”: {
“name”: “complete”,
“payload”: {
“doc”: ”${screen.FIRST_SCREEN.form.doc}”
}
}
}
]
}

|\ | `INVALID_ON_CLICK_ACTION_PAYLOAD` | The PhotoPicker component's value is not allowed in the payload of the navigate action. | The native component's value is not allowed in the payload of the navigate action. |

json {
“children”: [
{
“type”: “PhotoPicker”,
“name”: “photo”,
“label”: “PASS_CUSTOM_VALUE”
},
{
“type”: “Footer”,
“label”: “PASS_CUSTOM_VALUE”,
“on-click-action”: {
“name”: “navigate”,
“payload”: {
“photo”: ”${screen.FIRST_SCREEN.form.photo}”
}
}
}
]
}

|\ | `INVALID_ON_CLICK_ACTION_PAYLOAD` | The DocumentPicker component's value is not allowed in the payload of the navigate action. | The native component's value is not allowed in the payload of the navigate action. |

json {
“children”: [
{
“type”: “DocumentPicker”,
“name”: “doc”,
“label”: “PASS_CUSTOM_VALUE”
},
{
“type”: “Footer”,
“label”: “PASS_CUSTOM_VALUE”,
“on-click-action”: {
“name”: “navigate”,
“payload”: {
“doc”: ”${screen.FIRST_SCREEN.form.doc}”
}
}
}
]
} ``` |
\

Complete Action Errors\

| Error Code | Error Message | Details | Sample Flow JSON | \ | | ---------- | ------------- | ------- | ---------------- |
| INVALID_COMPLETE_ACTION | On-click-action ‘complete’ can only be configured on a terminal screen. | Complete action can only be in terminal screens |

json&lt;br /&gt;&#123;<br />  "version": "2.1",<br />  "screens": [<br />    &#123;<br />      "id": "FIRST_SCREEN",<br />      "layout": &#123;<br />        "type": "SingleColumnLayout",<br />        "children": [<br />          &#123;<br />            "type": "Footer",<br />            "on-click-action": &#123;<br />              "name": "complete",<br />              "payload": &#123;&#125;<br />            &#125;<br />          &#125;<br />        ]<br />      &#125;<br />    &#125;<br />  ]<br />&#125;&lt;br /&gt;

|
\

Navigate Action Errors\

| Error Code | Error Message | Details | Sample Flow JSON | \ | | ---------- | ------------- | ------- | ---------------- |
| INVALID_NAVIGATE_ACTION_PAYLOAD | No data model is defined in the next screen ‘(screenName)’. | Navigate action’s target screen does not have a data model.
In data channel less flows, data passed from the current screen must be used on the navigate action’s target screen.
If it is not required on the next screen but some screen later in the Flow, use global dynamic data binding to access the data from version 4.0 and above. |

json&lt;br /&gt;&#123;<br />  "version": "2.1",<br />  "screens": [<br />    &#123;<br />      "id": "FIRST_SCREEN",<br />      ...<br />        &#123;<br />          "on-click-action": &#123;<br />            "name": "navigate",<br />            "next": &#123;<br />              "type": "screen",<br />              "name": "SECOND_SCREEN"<br />            &#125;,<br />            "payload": &#123;<br />              "name": "some name"<br />            &#125;<br />          &#125;<br />        &#125;<br />    &#125;,<br />    &#123;<br />      "id": "SECOND_SCREEN",<br />      "layout": &#123;<br />        ...<br />      &#125;<br />    &#125;<br />  ]<br />&#125;&lt;br /&gt;

|
| INVALID_NAVIGATE_ACTION_PAYLOAD | Following fields are missing in the next screen’s data model: [fieldNames]. | Fields in the navigation action payload are missing in the next screen’s data model. |

json<br />  "version": "2.1",<br />  "screens": [<br />    &#123;<br />      "id": "FIRST_SCREEN",<br />      ...<br />        &#123;<br />          "on-click-action": &#123;<br />            "name": "navigate",<br />            "next": &#123;<br />              "type": "screen",<br />              "name": "SECOND_SCREEN"<br />            &#125;,<br />            "payload": &#123;<br />              "name": "some name"<br />            &#125;<br />          &#125;<br />        &#125;<br />    &#125;,<br />    &#123;<br />      "id": "SECOND_SCREEN",<br />      "data": &#123;&#125;,<br />      "layout": &#123;<br />        ...<br />      &#125;<br />    &#125;<br />  ]<br />&#125;&lt;br /&gt;

|
| INVALID_NAVIGATE_ACTION_PAYLOAD | Following fields are expected in the next screen’s data model but missing in payload: [fieldNames]. | Fields in the next screen’s data model are missing from navigate action’s payload. |

json&lt;br /&gt;&#123;<br />  "version": "2.1",<br />  "screens": [<br />    &#123;<br />      "id": "FIRST_SCREEN",<br />      ...<br />        &#123;<br />          "on-click-action": &#123;<br />            "name": "navigate",<br />            "next": &#123;<br />              "type": "screen",<br />              "name": "SECOND_SCREEN"<br />            &#125;,<br />            "payload": &#123;&#125;<br />          &#125;<br />        &#125;<br />    &#125;,<br />    &#123;<br />      "id": "SECOND_SCREEN",<br />      "data": &#123;<br />          "name": &#123;"type": "string"&#125;<br />      &#125;,<br />      "layout": &#123;<br />        ...<br />      &#125;<br />    &#125;<br />  ]<br />&#125;&lt;br /&gt;

|
| INVALID_NAVIGATE_ACTION_PAYLOAD | Schema of payload data at ‘

&#123;payloadField&#125;' on screen '

{payloadScreen}’ is not matching with schema of data model field on screen ‘

&#123;dataModelScreen&#125;'. Property is expecting '

{dataModelFieldType}’ but got ‘

&#123;payloadFieldType&#125;'. | Type of field in navigate action payload do not match that in next screen’s data model | ```json&lt;br /&gt;&#123;<br /> "version": "2.1",<br /> "screens": [<br /> &#123;<br /> "id": "FIRST_SCREEN",<br /> ...<br /> &#123;<br /> "on-click-action": &#123;<br /> "name": "navigate",<br /> "next": &#123;<br /> "type": "screen",<br /> "name": "SECOND_SCREEN"<br /> &#125;,<br /> "payload": &#123;<br /> "name": 123<br /> &#125;<br /> &#125;<br /> &#125;<br /> &#125;,<br /> &#123;<br /> "id": "SECOND_SCREEN",<br /> "data": &#123;<br /> "name": &#123;"type": "string"&#125;<br /> &#125;,<br /> "layout": &#123;<br /> ...<br /> &#125;<br /> &#125;<br /> ]<br />&#125;&lt;br /&gt;``` |\ | `INVALID_NAVIGATE_ACTION_NEXT_SCREEN_NAME` | Same screen navigation is not allowed. Loop detected at \[ScreenNames\]. | The source and target screen of navigate action are the same | ```json&lt;br /&gt;&#123;<br /> "version": "2.1",<br /> "screens": [<br /> &#123;<br /> "id": "FIRST_SCREEN",<br /> ...<br /> &#123;<br /> "on-click-action": &#123;<br /> "name": "navigate",<br /> "next": &#123;<br /> "type": "screen",<br /> "name": "FIRST_SCREEN"<br /> &#125;,<br /> "payload": &#123;&#125;<br /> &#125;<br /> &#125;<br /> &#125;<br /> ]<br />&#125;&lt;br /&gt;``` |\ | `INVALID_NAVIGATE_ACTION_NEXT_SCREEN_NAME` | Unknown screen ids found: \[screenNames\]. | The target screen of navigate action not present in flow json | ```json&lt;br /&gt;&#123;<br /> "version": "2.1",<br /> "screens": [<br /> &#123;<br /> "id": "FIRST_SCREEN",<br /> ...<br /> &#123;<br /> "on-click-action": &#123;<br /> "name": "navigate",<br /> "next": &#123;<br /> "type": "screen",<br /> "name": "not_present"<br /> &#125;,<br /> "payload": &#123;&#125;<br /> &#125;<br /> &#125;<br /> &#125;<br /> ]<br />&#125;&lt;br /&gt;``` |\ | `INVALID_NAVIGATE_ACTION_PAYLOAD` | Schema of dynamic data '

{payloadFieldValue}’ is not matching schema of data model field ‘

&#123;payloadField&#125;' on screen '

{dataModelScreen}’. Property is expecting ‘

&#123;dataModelFieldType&#125;' but got '

{payloadFieldType}’. | The type of dynamic binding in action payload does not match that in data model of next screen |

json&lt;br /&gt;&#123;<br />  "version":  "2.1",<br />  "screens":  [<br />    &#123;<br />      "id":  "FIRST_SCREEN",<br />      "layout":  &#123;<br />        "children":  [<br />          &#123;<br />            "type": "Form",<br />            "children": [<br />              &#123;<br />                "type": "TextInput",<br />                "name": "input"<br />              &#125;,<br />              &#123;<br />                "type":  "Footer",<br />                "label":  "Done",<br />                "on-click-action":  &#123;<br />                  "name":  "navigate",<br />                  "next": &#123;<br />                    "type": "screen",<br />                    "name": "SECOND_SCREEN"<br />                  &#125;,<br />                  "payload":  &#123;<br />                    "text": "$&#123;form.input&#125;"<br />                  &#125;<br />                &#125;<br />              &#125;<br />            ]<br />          &#125;<br />        ]<br />      &#125;<br />    &#125;,<br />    &#123;<br />      "id":  "SECOND_SCREEN",<br />      "title":  "Test",<br />      "terminal":  true,<br />      "data": &#123;<br />        "text": &#123;<br />          "type": "boolean",<br />          "__example__": true<br />        &#125;<br />      &#125;,<br />      ...<br />    &#125;<br />  ]<br />&#125;&lt;br /&gt;

|
| INVALID_ON_CLICK_ACTION_PAYLOAD | Missing Form component

&#123;expression&#125; for screen '

{screenId}’. | Form binding in action payload does not exist |

json&lt;br /&gt;&#123;<br />  "version":  "2.1",<br />  "screens":  [<br />    &#123;<br />      "id":  "FIRST_SCREEN",<br />      "layout":  &#123;<br />        ...<br />        &#123;<br />          "type": "Form",<br />          "children": [<br />            &#123;<br />              "type":  "Footer",<br />              "label":  "Done",<br />              "on-click-action":  &#123;<br />                "name":  "navigate",<br />                "payload":  &#123;<br />                  "text": "$&#123;form.not_present&#125;"<br />                &#125;<br />              &#125;<br />            &#125;<br />          ]<br />        &#125;,<br />      &#125;<br />    &#125;<br />  ]<br />&#125;&lt;br /&gt;

|
| INVALID_ON_CLICK_ACTION_PAYLOAD | Missing dynamic data ‘

&#123;expression&#125;' in the data model for screen

{screenId}. | Dynamic binding in action payload does not exist | TBD? |
| INVALID_ON_CLICK_ACTION_PAYLOAD | | Dynamic binding in action payload does not exist in the data model of the navigate action’s target screen. | |
| INVALID_ON_CLICK_ACTION_PAYLOAD | Invalid value found for the property ‘

&#123;propertyName&#125;'. | | |\ | `INVALID_ON_CLICK_ACTION_PAYLOAD` | Properties in navigate action payload differ from properties in data model of screen '

{screenName}’. | | |
| INVALID_ON_CLICK_ACTION_PAYLOAD | Value of ‘Form’ component cannot be used in form binding. | Dynamic binding in action payload references to form value |

json&lt;br /&gt;&#123;<br />  "version":  "2.1",<br />  "screens":  [<br />    &#123;<br />      "id":  "FIRST_SCREEN",<br />      "layout":  &#123;<br />        ...<br />        &#123;<br />          "type": "Form",<br />          "name": "form_name",<br />          "children": [<br />            &#123;<br />              "type":  "Footer",<br />              "label":  "Done",<br />              "on-click-action":  &#123;<br />                "name":  "navigate",<br />                "payload":  &#123;<br />                  "text": "$&#123;form.form_name&#125;"<br />                &#125;<br />              &#125;<br />            &#125;<br />          ]<br />        &#125;,<br />      &#125;<br />    &#125;<br />  ]<br />&#125;&lt;br /&gt;

|
\

Screen Data Model Errors\

| Error Code | Error Message | Details | Sample Flow JSON | \ | | ---------- | ------------- | ------- | ---------------- |
| INVALID_SCREEN_DYNAMIC_DATA | Missing dynamic data ‘

&#123;expression&#125;' in the screen data model. | dynamic data not present in data model | ```json&lt;br /&gt;&#123;<br /> "version": "2.1", <br /> "screens": [<br /> &#123;<br /> "id": "SCREEN_A",<br /> "title": "Test",<br /> "terminal": true,<br /> "layout": &#123;<br /> "type": "SingleColumnLayout",<br /> "children": [<br /> &#123;<br /> "type": "TextHeading",<br /> "text": "

{data.screen_title}”
}
]
}
}
]
}

|\ | `INVALID_SCREEN_DYNAMIC_DATA` | Expected '$&#123;dataModelPointer&#125;' to be of type '$&#123;expectedPropertyType&#125;'. | Type of dynamic data and type of its reference field in data model are not matched |

json {
“version”: “2.1”,
“screens”: [
{
“id”: “SCREEN_A”,
“data”: {
“top”: {
“type”: “object”,
“properties”: {
“secondLevel”: {
“type”: “object”,
“properties”: {
“target”: {
“type”: “boolean”
}
}
}
}
}
},
“layout”: {
“children”: [
{
“type”: “TextHeading”,
“text”: “

&#123;data.top.secondLevel.target&#125;"<br /> &#125;<br /> ]<br /> &#125;<br /> &#125;<br /> ]<br />&#125;&lt;br /&gt;``` |\ | `INVALID_SCREEN_DYNAMIC_DATA` | Data model schema is invalid for '

{expression}’. Missing schema for

&#123;objectProperty&#125;. | Required property of component’s field is not in schema defined in data model | ```json&lt;br /&gt;&#123;<br /> "version": "2.1",<br /> "screens": [<br /> &#123;<br /> "id": "SCREEN_A",<br /> "data": &#123;<br /> "products": &#123;<br /> "type": "array",<br /> "items": &#123;<br /> "type": "object",<br /> "properties": &#123;<br /> "id": &#123;<br /> "type": "string"<br /> &#125;<br /> &#125;<br /> &#125;,<br /> "__example__": []<br /> &#125;<br /> &#125;,<br /> "layout": &#123;<br /> "type": "SingleColumnLayout",<br /> "children": [<br /> &#123;<br /> "type": "Form",<br /> "children": [<br /> &#123;<br /> "type": "CheckboxGroup",<br /> "name": "PASS_CUSTOM_VALUE",<br /> "data-source": "

{data.products}”
}
]
}
]
}
}
]
}

|\ | `INVALID_SCREEN_DATA` | Property '__example__' is allowed only as a top level property of data model. Invalid entry: '(path to error)'. | ‘__example__’ can only be present in the top level fields of the data model. |

json {
“version”: “2.1”,
“screens”: [
{
“id”: “SCREEN_A”,
“data”: {
“initial_values”: {
“type”: “object”,
“properties”: {
“number”: {
“type”: “number”
},
“example”: {“number”: 8553906697}
},
“example”: {
“number”: 8553906697
}
}
},
…
}
]
}

|\ | `INVALID_SCREEN_DATA` | Missing the definition of property ‘type’. | Fields in data model must have ‘type’ property |

json {
“version”: “2.1”,
“screens”: [
{
“id”: “SCREEN_A”,
“data”: {
“name”: {}
},
…
}
]
}

|\ | `INVALID_SCREEN_DATA` | Expected the property ‘type’ to be of type string. | The value of the ‘type’ property in the data model must be of type ‘string’. |

json {
“version”: “2.1”,
“screens”: [
{
“id”: “SCREEN_A”,
“data”: {
“name”: {
“type”: 123
}
},
…
}
]
}

|\ | `INVALID_SCREEN_DATA` | Missing the schema for property 'items' in array. | The schema of ‘array’ type must have ‘items’ property |

json {
“version”: “2.1”,
“screens”: [
{
“id”: “SCREEN_A”,
“data”: {
“name”: {
“type”: “array”,
“example”: []
}
},
“layout”: {
“children”: […]
}
}
]
}

|\ | `INVALID_SCREEN_DATA` | Expected the property 'items' to be of type boolean or object. | The type of ‘items’ property can only be boolean or object |

json {
“version”: “2.1”,
“screens”: [
{
“id”: “SCREEN_A”,
“data”: {
“name”: {
“type”: “array”,
“items”: “string”,
“example”: []
}
},
“layout”: {
“children”: […]
}
}
]
}

|\ | `INVALID_SCREEN_DATA` | Invalid data model schema. Expected property '__example__' to be of type (type in schema), but found (actual type). | The type of ‘__example__’ property does not match schema definition |

json {
“version”: “2.1”,
“screens”: [
{
“id”: “SCREEN_A”,
“data”: {
“name”: {
“type”: “number”,
“example”: “123”
}
},
“layout”: {
“children”: […]
}
}
]
}

|\ | `INVALID_SCREEN_DATA` | Global Dynamic data ‘(expression)’ on screen ROOT does not exist, but is used on screen (screenID). | The data, which dynamic binding expression refers to, does not exist |

json {
“id”: “MAIN”,
“title”: “Title”,
“terminal”: true,
“layout”: {
“type”: “SingleColumnLayout”,
“children”: [
{
“type”: “Footer”,
“label”: “

&#123;screen.ROOT.form.intro_text.type&#125;",<br /> "on-click-action": &#123;<br /> "name": "complete",<br /> "payload": &#123;&#125;<br /> &#125;<br /> &#125;<br /> ]<br /> &#125;<br /> &#125;&lt;br /&gt;``` |\ | | Global dynamic data '

{expression}’ used on screen ‘

&#123;screenId&#125;' for

{componentType} property ‘

&#123;property&#125;' is invalid since screen '

{screenId}’ represents current screen. Convert expression to local referencing of the form

&#123;data.(property)&#125;.<br />Global dynamic data '

{expression}’ used on screen ‘

&#123;currentScreenId&#125;' for

{componentType} property ‘

&#123;property&#125;' is invalid since screen '

{referencedScreenId}’ is missing in the Flow JSON. | | |
| INVALID_SCREEN_DYNAMIC_DATA |

&#123;screen.ROOT.data.products.items.properties.title&#125; on screen 'ROOT' for TextHeading property 'text' is invalid as 'items' is defined in an array schema in the data model. | When the type of property using dynamic data (&#123;

data.val}) does not match the type specified in the data model.
For example, the TextHeading property ‘text’ expects a string value. If it is taking a dynamic data value whose type is an array, this error is returned. |

json&lt;br /&gt;&#123;<br />   "version": "4.0",<br />   "screens": [<br />     &#123;<br />       "id": "ROOT",<br />       "title": "Test",<br />       "data": &#123;<br />         "products": &#123;<br />           "type": "array",<br />           "items": &#123;<br />             "type": "object",<br />             "properties": &#123;<br />               "id": &#123;"type": "string"&#125;,<br />               "title": &#123;"type": "string"&#125;<br />             &#125;<br />           &#125;,<br />           "__example__": []<br />         &#125;<br />       &#125;,<br />       "layout": &#123;<br />         "type": "SingleColumnLayout",<br />         "children": [<br />           &#123;<br />             "type": "Footer",<br />             "label": "PASS_CUSTOM_VALUE",<br />             "on-click-action": &#123;<br />               "name": "navigate",<br />               "next": &#123;<br />                 "type": "screen",<br />                 "name": "MAIN_SCREEN"<br />               &#125;,<br />               "payload": &#123;&#125;<br />             &#125;<br />           &#125;<br />         ]<br />       &#125;<br />     &#125;,<br />     &#123;<br />       "id": "MAIN_SCREEN",<br />       "title": "Test",<br />       "terminal": true,<br />       "layout": &#123;<br />         "type": "SingleColumnLayout",<br />         "children": [<br />           &#123;<br />             "type": "TextSubheading",<br />             "text": "$&#123;screen.ROOT.data.products.items.properties.title&#125;"<br />           &#125;,<br />           &#123;<br />             "type": "Footer",<br />             "label": "PASS_CUSTOM_VALUE",<br />             "on-click-action": &#123;<br />               "name": "complete",<br />               "payload": &#123;&#125;<br />             &#125;<br />           &#125;<br />         ]<br />       &#125;<br />     &#125;<br />   ]<br /> &#125;&lt;br /&gt;

|
| INVALID_SCREEN_DYNAMIC_DATA | `

&#123;expression&#125; defined for screen '

{screenId}’

&#123;componentType&#125; property '

{componentProperty}’ is invalid as its schema is missing in the data model.` | When the type of property using dynamic data ({

data.val&#125;) is missing in the data model. | |\ | `INVALID_SCREEN_DYNAMIC_DATA` | Expected '

{dataModelPointer}’ to be of one of these types: [string, object]. | Properties like ‘error-message’ can only be of type string or object. |

json&lt;br /&gt;&#123;<br />   "version": "4.0",<br />   "data_api_version": "3.0",<br />   "routing_model": &#123;&#125;,<br />   "screens": [<br />     &#123;<br />       "id": "screenA",<br />       "title": "Screen Title",<br />       "terminal": true,<br />       "data": &#123;<br />           "error": &#123;<br />             "type": "boolean",<br />             "__example__": true<br />           &#125;<br />       &#125;,<br />       "layout": &#123;<br />         "type": "SingleColumnLayout",<br />         "children": [<br />           &#123;<br />             "type": "PhotoPicker",<br />             "name": "photo",<br />             "label": "Add ID proof",<br />             "error-message": "$&#123;data.error&#125;"<br />           &#125;<br />         ]<br />       &#125;<br />     &#125;<br />   ]<br /> &#125;&lt;br /&gt;

|
\

Min Max Limit Violation Errors\

| Error Code | Error Message | Details | Sample Flow JSON | \ | | ---------- | ------------- | ------- | ---------------- |
| MAX_SCREENS_NUMBER | Maximum number of screens allowed per Flow is 100 but found (actualCount). | A Flow cannot have more than 100 screens. | A Flow with more than 100 screens.

json&lt;br /&gt;&#123;<br />  "version": "2.1",<br />  "screens": [<br />    &#123;<br />      "id": "SCREEN_ONE",<br />       ...<br />    &#125;,<br />    ...<br />    &#123;<br />      "id": "SCREEN_HUNDRED_ONE",<br />       ...<br />    &#125;<br />  ]<br />&#125;&lt;br /&gt;

|
| MAX_EMBEDDED_LINK_PER_SCREEN
MAX_FOOTER_PER_SCREEN
MAX_IMAGE_PER_SCREEN
MAX_OPT_IN_PER_SCREEN | Maximum number of (componentName) allowed per screen is (maxAllowedCount) but found (actualCount). | Limit on the count of certain components that be added per screen is as follows-
Footer
1
EmbeddedLink
2
Image
3
OptIn
5 |

json&lt;br /&gt;&#123;<br />  "version": "2.1",<br />  "screens": [<br />    {<br />      "id": "screenA",<br />      "refresh_on_back": true,<br />      "layout": {<br />        "children": [<br />          {<br />            "type": "Footer",<br />            "label": "Submit",<br />            "on-click-action": {<br />               "name": "complete",<br />                "payload": {}<br />             }<br />           },<br />          {<br />            "type": "Footer",<br />            "label": "Submit",<br />            "on-click-action": {<br />               "name": "complete",<br />                "payload": {}<br />             }<br />           }<br />         ]<br />      }<br />    }<br />  ]<br />&#125;&lt;br /&gt;

|
| MIN_VALUE_GREATER_THAN_MAX | (min_attribute_name) cannot be greater than (max_attribute_name) for (component_type) (component_name). | Components that have a minimum and maximum attribute (eg. min / max length, min-selected-items / max-selected-items) should not allow the min attribute’s value to be greater than the max attribute’s value. |

json&lt;br /&gt;&#123;<br />  "screens": [<br />    {<br />      "id": "FIRST_SCREEN",<br />      "layout": {<br />        "children": [<br />          {<br />            "type": "Form",<br />            "name": "PASS_CUSTOM_VALUE",<br />            "children": [<br />               {<br />                 "type": "CheckboxGroup",<br />                 "name": "cbg",<br />                 "min-selected-items": 3,<br />                 "max-selected-items": 2,<br />                 "data-source": [<br />                    {<br />                       "id":"1",<br />                       "title":"Title 1"<br />                     },<br />                     {<br />                       "id": "2", <br />                       "title": "Title 2"<br />                     },<br />                     {<br />                       "id": "3", <br />                       "title": "Title 3"<br />                     }<br />                   ]<br />                 }<br />               ]<br />            },<br />        ]<br />      }<br />    }<br />  ]<br />&#125;&lt;br /&gt;

|
| MINIMUM_VALUE_REQUIRED
MAXIMUM_VALUE_REQUIRED | The minimum value allowed for property ’

{propertyName}' is

.
The maximum value allowed for property ’

{propertyName}' is

. | Some attributes are required to have a value between a range (min,max).
For example, min-uploaded-photos in PhotoPicker must be between [0, 30]. |

json&lt;br /&gt;&#123;<br />  "screens": [<br />    {<br />      "id": "FIRST_SCREEN",<br />      "layout": {<br />        "children": [<br />          {<br />            "type": "PhotoPicker",<br />            "name": "ID_Proof",<br />            "min-uploaded-photos": -1,<br />            "max-uploaded-photos": 40,<br />            ...<br />          },<br />          ...<br />        ]<br />      }<br />    }<br />  ]<br />&#125;&lt;br /&gt;

|
\

Data_api_version | Refresh_on_back errors\

| Error Code | Error Message | Details | Sample Flow JSON | \ | | ---------- | ------------- | ------- | ---------------- |
| MISSING_REQUIRED_PROPERTY | The property ‘data_api_version’ is required for data_exchange action. | Action data_exchange cannot be executed without a server endpoint.
Property ‘data_api_version’ indicates that Flow is connected to a server. |

json&lt;br /&gt;&#123;<br />  "version": "2.1",<br />  "screens": [<br />    {<br />      "id": "screenA",<br />      "title": "screenTitle",<br />      "type": "SingleColumnLayout",<br />      "layout": {<br />        "children": [<br />          {<br />            "type": "Footer",<br />            "label": "Submit",<br />            "on-click-action": {<br />               "name": "data_exchange",<br />                "payload": {}<br />             }<br />           }<br />         ]<br />      }<br />    }<br />  ]<br />&#125;&lt;br /&gt;

Missing data_api_version when using action data_exchange. |
| MISSING_REQUIRED_PROPERTY | The property ‘routing_model’ is required for property ‘data_api_version’. | Action data_exchange cannot be executed without a routing_model. |

json&lt;br /&gt;&#123;<br />  "version": "2.1",<br />  "screens": [<br />    {<br />      "id": "screenA",<br />      "title": "screenTitle",<br />      "layout": {<br />        "type": "SingleColumnLayout",<br />        "children": [<br />          {<br />            "type": "Footer",<br />            "label": "Submit",<br />            "on-click-action": {<br />               "name": "data_exchange",<br />                "payload": {}<br />             }<br />           }<br />         ]<br />      }<br />    }<br />  ]<br />&#125;&lt;br /&gt;

|
| INVALID_PROPERTY_VALUE | Property ‘refresh_on_back’ can be true only when property ‘data_api_version’ is set. | Data channel less flows i.e. Flows without an endpoint setup are not allowed to set property refresh_on_back as true.If a Flow does not have property ‘data_api_version’ set, it is considered a data channel less flow. |

json&lt;br /&gt;&#123;<br />  "version": "2.1",<br />  "screens": [<br />    {<br />      "id": "screenA",<br />      "refresh_on_back": true,<br />      "layout": {<br />        "children": [...]<br />      }<br />    }<br />  ]<br />&#125;&lt;br /&gt;

|
\

Naming Errors\

| Error Code | Error Message | Details | Sample Flow JSON | \ | | ---------- | ------------- | ------- | ---------------- |
| DUPLICATE_FORM_COMPONENT_NAMES | Duplicate name found for Form components: (duplicateName). | Components inside a Form must have unique names. |

json&lt;br /&gt;&#123;<br />      "version": "2.1",<br />      "screens": [<br />        {<br />          "id": "screenA",<br />          "title": "Screen Title",<br />          "terminal": true,<br />          "layout": {<br />            "type": "SingleColumnLayout",<br />            "children": [<br />              {<br />                "type": "Form",<br />                "name": "form",<br />                "children": [<br />                  {<br />                    "name": "textInput",<br />                    "type": "TextInput",<br />                    "label": "Text 1"<br />                  },<br />                  {<br />                    "name": "textInput",<br />                    "type": "TextInput",<br />                    "label": "Text 2"<br />                  }<br />                ]<br />              }<br />              ...<br />            ]<br />          }        <br />        }<br />      ]<br />    &#125;&lt;br /&gt;

|
| DUPLICATE_FORM_COMPONENT_NAMES | Duplicate name found for Form components: (duplicateName). | Components inside a Form must have unique names inside all If and switch branches. |

json&lt;br /&gt;&#123;<br />  "version": "4.0",<br />  "screens": [<br />    {<br />      "id": "PATH_SIMULATION",<br />      "layout": {<br />        "type": "SingleColumnLayout",<br />        "children": [<br />          {<br />            "type": "If",<br />            "then": [<br />              {<br />                "type": "OptIn",<br />                "name": "name"<br />              }<br />            ],<br />            "else": [<br />              {<br />                "type": "TextInput",<br />                "name": "name1"<br />              }<br />            ]<br />          },<br />          {<br />            "type": "Switch",<br />            "cases": {<br />              "case1": [<br />                {<br />                  "type": "DatePicker",<br />                  "name": "name"<br />                }<br />              ],<br />              "case2": [<br />                {<br />                  "type": "TextArea",<br />                  "name": "name1"<br />                }<br />              ]<br />            }<br />          },<br />          {<br />            "type": "Form",<br />            "children": [<br />              {<br />                "name": "name"<br />              },<br />              {<br />                "name": "name1"<br />              }<br />            ]<br />          }<br />        ]<br />      }<br />    }<br />  ]<br />}{<br />  "version": "4.0",<br />  "screens": [<br />    {<br />      "id": "PATH_SIMULATION",<br />      "layout": {<br />        "type": "SingleColumnLayout",<br />        "children": [<br />          {<br />            "type": "If",<br />            "then": [<br />              {<br />                "type": "OptIn",<br />                "name": "name"<br />              }<br />            ],<br />            "else": [<br />              {<br />                "type": "TextInput",<br />                "name": "name1"<br />              }<br />            ]<br />          },<br />          {<br />            "type": "Switch",<br />            "cases": {<br />              "case1": [<br />                {<br />                  "type": "DatePicker",<br />                  "name": "name"<br />                }<br />              ],<br />              "case2": [<br />                {<br />                  "type": "TextArea",<br />                  "name": "name1"<br />                }<br />              ]<br />            }<br />          },<br />          {<br />            "type": "Form",<br />            "children": [<br />              {<br />                "name": "name"<br />              },<br />              {<br />                "name": "name1"<br />              }<br />            ]<br />          }<br />        ]<br />      }<br />    }<br />  ]<br />&#125;&lt;br /&gt;

json&lt;br /&gt;&#123;<br />      "version": "2.1",<br />      "screens": [<br />        {<br />          "id": "screenA",<br />           ...    <br />        },<br />        {<br />          "id": "screenA",<br />           ...    <br />        }<br />      ]<br />  &#125;&lt;br /&gt;

|
| SCREEN_ID_IS_RESERVED_KEYWORD | Screen id cannot be ‘success’ since it is a reserved keyword. | ‘success’ is a reserved keyword for receiving termination response’s next screen in data_exchange action. |

json&lt;br /&gt;&#123;<br />      "version": "2.1",<br />      "screens": [<br />        {<br />          "id": "success",<br />           ...    <br />        }<br />      ]<br />  &#125;&lt;br /&gt;

|
\

Terminal Screen Errors\

| Error Code | Error Message | Details | Sample Flow JSON | \ | | ---------- | ------------- | ------- | ---------------- |
| MISSING_FOOTER_ON_TERMINAL_SCREEN | Footer component is missing on terminal screens: (screen IDs). | Terminal screen must have a Footer component to be able to terminate the Flow. |

json&lt;br /&gt;&#123;<br />      "version": "2.1",<br />      "screens": [<br />        {<br />          "id": "screenA",<br />          "title": "Screen Title",<br />          "terminal": true,<br />          "layout": {<br />            "type": "SingleColumnLayout",<br />            "children": [<br />              {<br />                "type": "TextHeading",<br />                "text": "Heading"<br />              }<br />            ]<br />          }        <br />        }<br />      ]<br />  &#125;&lt;br /&gt;

json&lt;br /&gt;&#123;<br />      "version": "2.1",<br />      "screens": [<br />        {<br />          "id": "screenA",<br />          "title": "Screen Title",<br />          "layout": {<br />            "type": "SingleColumnLayout",<br />            "children": [..]<br />          }        <br />        }<br />      ]<br />  &#125;&lt;br /&gt;

|
\

Optional Form\

| Error Code | Error Message | Details | Sample Flow JSON | \ | | ---------- | ------------- | ------- | ---------------- |
| COMPONENTS_OUTSIDE_FORM | Component ‘

&#123;components.join(\`', '\`)&#125;' is not allowed outside Form when Form component is present.<br />Components '

{components.join(`’, ’`)}’ are not allowed outside Form when Form component is present. | Any Form component cannot exist outside Form when Form exists on the screen.
Form components are the ones which can take user inputs. |

json&lt;br /&gt;&#123;<br />    "version": "4.0",<br />    "screens": [<br />      &#123;<br />        "layout": &#123;<br />          "type": "SingleColumnLayout",<br />          "children": [<br />            &#123;<br />              "type": "TextInput",<br />              "name": "path2",<br />              "label": "Path"<br />            &#125;,<br />            &#123;<br />              "type": "Form",<br />              "name": "flow_path",<br />              "children": [<br />                &#123;<br />                  "type": "TextInput",<br />                  "name": "path",<br />                  "label": "Path"<br />                &#125;,<br />                ...<br />            &#125;<br />          ]<br />       &#125;<br />    &#125;<br />&#125;&lt;br /&gt;

|
\
| Error Code | Error Message | Details | Sample Flow JSON | \ | | ---------- | ------------- | ------- | ---------------- |
| MISSING_FOOTER_IN_IF_ELSE_BRANCHES | Missing Footer inside one of the ‘If’ component branches. Branch ‘else’ should exist and contain one Footer. | There is a footer inside ‘then’ branch of IF component, which does not have ‘else’ branch |

json&lt;br /&gt;&#123;<br />    "version": "4.0",<br />    "screens": [<br />      &#123;<br />        "id": "PATH_SIMULATION",<br />        "layout": &#123;<br />          "type": "SingleColumnLayout",<br />          "children": [<br />            &#123;<br />              "type": "If",<br />              "condition": "\$&#123;data.ti&#125;",<br />              "then": [<br />                &#123;<br />                  "type": "Footer",<br />                  "label": "PASS_CUSTOM_VALUE",<br />                  "on-click-action": &#123;<br />                    "name": "complete",<br />                    "payload": &#123;&#125;<br />                  &#125;<br />                &#125;<br />              ]<br />            &#125;<br />          ]<br />        &#125;<br />      &#125;<br />    ]<br />  &#125;&lt;br /&gt;

|
| MISSING_FOOTER_IN_IF_ELSE_BRANCHES | Footer component must be present in all branches of ‘If’ component if it exists in any one branch. | There is a footer inside ‘then’ branch of IF component, but ‘else’ branch does not have |

json&lt;br /&gt;&#123;<br />    "version": "4.0",<br />    "screens": [<br />      &#123;<br />        "id": "PATH_SIMULATION",<br />        "title": "Title",<br />        "terminal": true,<br />        "data": &#123;<br />          "ti": &#123;"type": "boolean", "__example__": true&#125;<br />        &#125;,<br />        "layout": &#123;<br />          "type": "SingleColumnLayout",<br />          "children": [<br />            &#123;<br />              "type": "If",<br />              "condition": "\$&#123;data.ti&#125;",<br />              "then": [<br />                &#123;<br />                  "type": "TextInput",<br />                  "label": "PASS_CUSTOM_VALUE",<br />                  "name": "PASS_CUSTOM_VALUE"<br />                &#125;<br />              ],<br />              "else": [<br />                &#123;<br />                  "type": "Footer",<br />                  "label": "PASS_CUSTOM_VALUE",<br />                  "on-click-action": &#123;<br />                    "name": "complete",<br />                    "payload": &#123;&#125;<br />                  &#125;<br />                &#125;<br />              ]<br />            &#125;<br />          ]<br />        &#125;<br />      &#125;<br />    ]<br />  &#125;&lt;br /&gt;

|
| MISSING_FOOTER_IN_SWITCH_BRANCHES | Footer component must be present in all switch cases if it exists in one of the cases. | Part of branches of Switch component have footer, but others do not have |

json&lt;br /&gt;&#123;<br />    "version": "4.0",<br />    "screens": [<br />      &#123;<br />        "id": "PATH_SIMULATION",<br />        "layout": &#123;<br />          "type": "SingleColumnLayout",<br />          "children": [<br />            &#123;<br />              "type": "Switch",<br />              "value": "\$&#123;data.ti&#125;",<br />              "cases": &#123;<br />                "case1": [],<br />                "case2": [<br />                  &#123;<br />                    "type": "Footer",<br />                    "label": "PASS_CUSTOM_VALUE",<br />                    "on-click-action": &#123;<br />                      "name": "complete",<br />                      "payload": &#123;&#125;<br />                    &#125;<br />                  &#125;<br />                ],<br />                "case3": [<br />                  &#123;<br />                    "type": "TextInput",<br />                    "label": "PASS_CUSTOM_VALUE",<br />                    "name": "PASS_CUSTOM_VALUE"<br />                  &#125;<br />                ]<br />              &#125;<br />            &#125;<br />          ]<br />        &#125;<br />      &#125;<br />    ]<br />  &#125;&lt;br /&gt;

|
| MORE_THAN_ONE_FOOTER | Maximum number of Footer component allowed per screen is 1. | Screen contains more than one footer considering all branches of if and switch components. |

json&lt;br /&gt;&#123;<br />    "version": "4.0",<br />    "screens": [<br />      &#123;<br />        "id": "PATH_SIMULATION",<br />        "layout": &#123;<br />          "type": "SingleColumnLayout",<br />          "children": [<br />            &#123;<br />              "type": "Switch",<br />              "value": "$&#123;data.ti&#125;",<br />              "cases": &#123;<br />                "case1": [<br />                  &#123;<br />                    "type": "Footer",<br />                    "label": "PASS_CUSTOM_VALUE",<br />                    "on-click-action": &#123;<br />                      "name": "complete",<br />                      "payload": &#123;&#125;<br />                    &#125;<br />                  &#125;<br />                ],<br />                "case2": [<br />                  &#123;<br />                    "type": "Footer",<br />                    "label": "PASS_CUSTOM_VALUE",<br />                    "on-click-action": &#123;<br />                      "name": "complete",<br />                      "payload": &#123;&#125;<br />                    &#125;<br />                  &#125;<br />                ]<br />              &#125;<br />            &#125;,<br />            &#123;<br />              "type": "Footer",<br />              "label": "PASS_CUSTOM_VALUE",<br />              "on-click-action": &#123;<br />                "name": "complete",<br />                "payload": &#123;&#125;<br />              &#125;<br />            &#125;<br />          ]<br />        &#125;<br />      &#125;<br />    ]<br />  &#125;&lt;br /&gt;

|
\

“IF” Component Errors\

| Error Code | Error Message | Details | Sample Flow JSON | \ | | ---------- | ------------- | ------- | ---------------- |
| INVALID_PROPERTY_VALUE | Expected array to contain at least one component. | Property ‘then’ inside ‘If’ component must contain at least one component to display if property ‘condition’ is true. |

json&lt;br /&gt;&#123;<br />    "version": "4.0",<br />    "screens": [<br />      &#123;<br />        "id": "SCREEN_A",<br />        "layout": &#123;<br />          "type": "SingleColumnLayout",<br />          "children": [<br />            &#123;<br />              "type": "If",<br />              "condition": "$&#123;data.val&#125;",<br />              "then": []<br />            &#125;<br />          ]<br />        &#125;<br />      &#125;<br />    ]<br />  &#125;&lt;br /&gt;

|
| INVALID_PROPERTY_VALUE | Expected property ‘condition’ to contain at least one operand. | Property ‘condition’ cannot be blank or empty. It should either contain a valid expression or a single boolean operand. |

json&lt;br /&gt;&#123;<br />    "version": "4.0",<br />    "screens": [<br />      &#123;<br />        "id": "SCREEN_A",<br />        "layout": &#123;<br />          "type": "SingleColumnLayout",<br />          "children": [<br />            &#123;<br />              "type": "If",<br />              "condition": " ",<br />              "then": [...]<br />            &#125;<br />          ]<br />        &#125;<br />      &#125;<br />    ]<br />  &#125;&lt;br /&gt;

|
| INVALID_PROPERTY_VALUE | Found invalid empty parentheses at column (col). | Property ‘condition’ cannot be blank or empty. It should either contain a valid expression or a single boolean operand. |

json&lt;br /&gt;&#123;<br />    "version": "4.0",<br />    "screens": [<br />      &#123;<br />        "id": "SCREEN_A",<br />        "layout": &#123;<br />          "type": "SingleColumnLayout",<br />          "children": [<br />            &#123;<br />              "type": "If",<br />              "condition": "( )",<br />              "then": [...]<br />            &#125;<br />          ]<br />        &#125;<br />      &#125;<br />    ]<br />  &#125;&lt;br /&gt;

|
| INVALID_PROPERTY_VALUE | An operator cannot not have literals on both sides. Found invalid syntax at column (col). | Property ‘condition’ cannot have literals on both ends of an operator since that condition always evaluates to the same result. |

json&lt;br /&gt;&#123;<br />    "version": "4.0",<br />    "screens": [<br />      &#123;<br />        "id": "SCREEN_A",<br />        "layout": &#123;<br />          "type": "SingleColumnLayout",<br />          "children": [<br />            &#123;<br />              "type": "If",<br />              "condition": "573 == 376",<br />              "then": [...]<br />            &#125;<br />          ]<br />        &#125;<br />      &#125;<br />    ]<br />  &#125;&lt;br /&gt;

|
| INVALID_PROPERTY_VALUE | Missing opening parenthesis for the closing parenthesis at column (col).
Missing closing parenthesis.
Missing closing quote for string.
Missing operator between ‘

&#123;firstValue&#125;' and '

{secondValue}’.
Invalid operator ‘

&#123;operator&#125;' found at column (col).<br />Invalid operand format '

{operand}’ found at column (col).
Unexpected character ‘

&#123;character&#125;' found at column (col).<br />Wrong positioning of operator '

{operator}’. It cannot be used in concatenation with ‘

&#123;firstValue&#125;'.<br />"Wrong positioning of operator '\|\|'. It cannot be used after '

{data.string_value}’ at column 21.”
Type mismatch in an equality operation between ‘

&#123;firstValue&#125;' and '

{secondValue}’ at column (col).
Invalid literal ‘

&#123;literal&#125;'.<br />Missing operand after last operator '

{operator}’. | Property ‘condition’ should have valid expression syntax. |

json&lt;br /&gt;&#123;<br />    "version": "4.0",<br />    "screens": [<br />      &#123;<br />        "id": "SCREEN_A",<br />        "layout": &#123;<br />          "type": "SingleColumnLayout",<br />          "children": [<br />            &#123;<br />              "type": "If",<br />              "condition": "))$&#123;data.value_1&#125;((",<br />              "then": [...]<br />            &#125;<br />          ]<br />        &#125;<br />      &#125;<br />    ]<br />  &#125;&lt;br /&gt;

|
| INVALID_PROPERTY_VALUE | A numerical value is expected to follow the negative sign. | |

json&lt;br /&gt;&#123;<br />    "version": "4.0",<br />    "screens": [<br />      &#123;<br />        "id": "SCREEN_A",<br />        "layout": &#123;<br />          "type": "SingleColumnLayout",<br />          "children": [<br />            &#123;<br />              "type": "If",<br />              "condition": "$&#123;data.val&#125; ) -a",<br />              "then": [...]<br />            &#125;<br />          ]<br />        &#125;<br />      &#125;<br />    ]<br />  &#125;&lt;br /&gt;

json&lt;br /&gt;&#123;<br />    "version": "4.0",<br />    "screens": [<br />      &#123;<br />        "id": "SCREEN_A",<br />        "layout": &#123;<br />          "type": "SingleColumnLayout",<br />          "children": [<br />            &#123;<br />              "type": "If",<br />              "condition": "(($&#123;data.string_value&#125;))",<br />              "then": [...]<br />            &#125;<br />          ]<br />        &#125;<br />      &#125;<br />    ]<br />  &#125;&lt;br /&gt;

|
| INVALID_PROPERTY_VALUE | The only operand is a literal value. Expected single operand to be a boolean. | |

json&lt;br /&gt;&#123;<br />    "version": "4.0",<br />    "screens": [<br />      &#123;<br />        "id": "SCREEN_A",<br />        "layout": &#123;<br />          "type": "SingleColumnLayout",<br />          "children": [<br />            &#123;<br />              "type": "If",<br />              "condition": "true",<br />              "then": [...]<br />            &#125;<br />          ]<br />        &#125;<br />      &#125;<br />    ]<br />  &#125;&lt;br /&gt;

|
\

Switch Component Errors\

| Error Code | Error Message | Details | Sample Flow JSON | \ | | ---------- | ------------- | ------- | ---------------- |
| MISSING_FOOTER_IN_SWITCH_BRANCHES | Footer component must be present in all switch cases if it exists in any one case. | Part of branches of Switch component have footer, but others do not have |

json&lt;br /&gt;&#123;<br />    "version": "4.0",<br />    "screens": [<br />      &#123;<br />        "id": "PATH_SIMULATION",<br />        "layout": &#123;<br />          "type": "SingleColumnLayout",<br />          "children": [<br />            &#123;<br />              "type": "Switch",<br />              "value": "$&#123;data.ti&#125;",<br />              "cases": &#123;<br />                "case1": [],<br />                "case2": [<br />                  &#123;<br />                    "type": "Footer",<br />                    "label": "Submit",<br />                    "on-click-action": &#123;<br />                      "name": "complete",<br />                      "payload": &#123;&#125;<br />                    &#125;<br />                  &#125;<br />                ],<br />                "case3": [<br />                  &#123;<br />                    "type": "TextInput",<br />                    "label": "input",<br />                    "name": "Add name"<br />                  &#125;<br />                ]<br />              &#125;<br />            &#125;<br />          ]<br />        &#125;<br />      &#125;<br />    ]<br />  &#125;&lt;br /&gt;

|
\

Native Component Errors\

| Error Code | Error Message | Details | Sample Flow JSON | \ | | ---------- | ------------- | ------- | ---------------- |
| NATIVE_COMPONENT_IN_FORM_INIT_VALUES | Property ‘init-values’ should not contain value for components: [(native components’ type)]. | User tries to initialize native components via the “init-values” property of Form component.
However, native components like PhotoPicker and DocumentPicker cannot be initialized via init-values. |

json&lt;br /&gt;&#123;<br />    "version": "4.0",<br />    "screens": [<br />      &#123;<br />        "id": "MAIN_SCREEN",<br />        "layout": &#123;<br />          "type": "SingleColumnLayout",<br />          "children": [<br />            &#123;<br />              "type": "Form",<br />              "name": "PASS_CUSTOM_VALUE",<br />              "init-values": &#123;"photo": "abc", "doc": "efg"&#125;,<br />              "children": [<br />                &#123;<br />                  "type": "PhotoPicker",<br />                  "name": "photo",<br />                  "label": "Add your picture"<br />                &#125;,<br />                &#123;<br />                  "type": "DocumentPicker",<br />                  "name": "doc",<br />                  "label": "Add ID proof"<br />                &#125;<br />              ]<br />            &#125;,<br />            ......<br />          ]<br />        &#125;<br />      &#125;<br />    ]<br />  &#125;&lt;br /&gt;

|
| INVALID_ON_CLICK_ACTION_PAYLOAD | The value of

&#123;componentType&#125; component is not allowed in the payload of navigate action. | Values of native components (PhotoPicker and DocumentPicker) cannot be passed to any other screen using navigate action payload.<br />Use global data to access native components from one screen in another. | ```json&lt;br /&gt;&#123;<br /> "screens": [<br /> &#123;<br /> "id": "FIRST_SCREEN",<br /> "layout": &#123;<br /> "children": [<br /> &#123;<br /> "type": "PhotoPicker",<br /> "name": "photoPicker",<br /> "label": "PASS_CUSTOM_VALUE"<br /> &#125;,<br /> &#123;<br /> "type": "Footer",<br /> "on-click-action": &#123;<br /> "name": "navigate",<br /> "next": &#123;<br /> "name": "SECOND_SCREEN",<br /> "type": "screen"<br /> &#125;,<br /> "payload": &#123;<br /> "photo": "

{form.photoPicker}”
}
}
}
]
}
},
{
“id”: “SECOND_SCREEN”,
…
}
]
}

|\ | `INVALID_ON_CLICK_ACTION_PAYLOAD` | The value of following components must be a top-level string in complete and data_exchange on-click-action payload: : \[PhotoPicker, DocumentPicker\]. | PhotoPicker and DocumentPicker component value can only be used as a top-level string property in the on-click-action payload. |

json {
“children”: [
{
“type”: “DocumentPicker”,
“name”: “doc”,
“label”: “Add ID proof”
},
{
“type”: “Footer”,
“label”: “Submit”,
“on-click-action”: {
“name”: “navigate”,
“payload”: {
“doc”: {“first”: {“second”: [“in_array”, “

&#123;screen.FIRST_SCREEN.form.doc&#125;"]&#125;&#125;<br /> &#125;<br /> &#125;<br /> &#125;<br /> ]<br />&#125;&lt;br /&gt;```<br />```json&lt;br /&gt;&#123;<br /> "children": [<br /> &#123;<br /> "type": "PhotoPicker",<br /> "name": "photo",<br /> "label": "Add your picture"<br /> &#125;,<br /> &#123;<br /> "type": "Footer",<br /> "label": "Submit",<br /> "on-click-action": &#123;<br /> "name": "navigate",<br /> "payload": &#123;<br /> "photo": &#123;"first": &#123;"second": ["in_array", "

{screen.FIRST_SCREEN.form.photo}”]}}
}
}
}
]
}

|\ | `INVALID_ON_CLICK_ACTION_PAYLOAD` | PhotoPicker can only be used in complete action payload if value of property 'max-uploaded-photos' doesn't exceed 1. Default value is 30.<br />DocumentPicker can only be used in complete action payload if value of property 'max-uploaded-documents' doesn't exceed 1. Default value is 30. | If the property ‘max-uploaded-photo’ or ‘max-uploaded-documents’ have not been defined in the component, default value of 30 is considered. |

json {
“screens”: [
{
“id”: “FIRST_SCREEN”,
“layout”: {
“children”: [
{
“type”: “PhotoPicker”,
“name”: “photoPicker”,
“label”: “photoLabel”
},
{
“type”: “DocumentPicker”,
“name”: “DocumentPicker”,
“label”: “DocLabel”,
“max-uploaded-documents”: 3
},
{
“type”: “Footer”,
“on-click-action”: {
“name”: “complete”,
“payload”: {
“photo”: “

&#123;form.photoPicker&#125;",<br /> "doc": "

{form.DocumentPicker}”
}
}
}
]
}
}
]
}

|\ | `INVALID_ON_CLICK_ACTION_PAYLOAD` | Complete action payload can contain either a single PhotoPicker or a single DocumentPicker component. |  |

&#123;form.photoPicker&#125;",<br /> "doc": "

{form.DocumentPicker}”
}
}
}
]
}
}
]
} ``` |
| | | | |
\

Action errors\

| Error Code | Error Message | Details | Sample Flow JSON | \ | | ---------- | ------------- | ------- | ---------------- |
| INVALID_ACTION_PAYLOAD_PROPERTY | The following property (property) does not exist in the screen data model | The property for the payload as part of an action is not valid. This means the value for that property could not be parsed, for example if it references a property that doesn’t exist in the data model. |

json&lt;br /&gt;&#123;<br />  ...<br />  "data": &#123;&#125;,<br />  ...<br />  "on-unselect-action": &#123;<br />    "name": "update_data",<br />    "payload": &#123;<br />      "property": "`$&#123;data.value_that_does_not_exist_in_data_model&#125;`"<br />    &#125;<br />  &#125;,<br />&#125;&lt;br /&gt;

|

←\ \ Previous\ \ Flows API

→\ \ Next\ \ Versioning

On This Page

Error Codes

Flow Management API Error Codes

Business Endpoint Error Codes

On-Premise WhatsApp Business API Client Error Codes

Cloud API Error Codes

Error Types Reported via WebHook Alerts or Propagated Back to Endpoint

Static Validation Errors

Schema Validation Errors

FLow JSON Version Errors

Routing Model Errors

On-click Action Errors

Complete Action Errors

Navigate Action Errors

Screen Data Model Errors

Min Max Limit Violation Errors

Data_api_version | Refresh_on_back errors

Naming Errors

Terminal Screen Errors

Optional Form

Footer Errors

”IF” Component Errors

Switch Component Errors

Native Component Errors

Action errors

​Error Codes

​Flow Management API Error Codes

​Business Endpoint Error Codes

​On-Premise WhatsApp Business API Client Error Codes

​Cloud API Error Codes

​Error Types Reported via WebHook Alerts or Propagated Back to Endpoint

​Static Validation Errors

​Schema Validation Errors

​FLow JSON Version Errors\

​Routing Model Errors\

​On-click Action Errors\

​Complete Action Errors\

​Navigate Action Errors\

​Screen Data Model Errors\

​Min Max Limit Violation Errors\

​Data_api_version | Refresh_on_back errors\

​Naming Errors\

​Terminal Screen Errors\

​Optional Form\

​Footer Errors\

​“IF” Component Errors\

​Switch Component Errors\

​Native Component Errors\

​Action errors\