Deployment validation errors
In Connector Builder, the Deployment page lists the current deployed and test versions of a connector, and a history of previous deployments.
If a deployment fails, then Connector Builder returns a validation error message to explain the cause.
Hard Validations
Hard validations indicate a failed connector deployment. If Connector Builder returns a validation error message from this table when you try to deploy your connector, then you must correct the issue before you can complete a successful deployment.
|
Reference code |
Validation error |
Description |
|---|---|---|
|
|
|
Each active action flow must have a unique name. For example, your connector project can't have two action flows named Create User. Either change the name for one of the flows or deactivate it. |
|
|
|
A system event card such as a connector Authping or a connector action card must trigger a flow. Update your flow as needed with one of these cards. If necessary, delete the system event card, add it again, and replace any mappings from the event card. |
|
|
|
A name of a flow can contain letters, numbers, and spaces only. Leading or trailing spaces and any other characters are prohibited. Remove unsupported characters from the name of the flow. |
|
|
|
A connector project can have one Authping flow only. Deactivate or delete other Authping flows. |
|
|
|
Connector Builder reserves the term _authping for Authping flows only. Replace the term with another string, or add characters to the name of the flow. Optionally, deactivate or delete the flow. |
|
|
|
A connector can have one Revoke flow only. Deactivate or delete other Revoke flows. |
|
|
|
Connector Builder reserves the term _revoke for Revoke flows only. Replace the term with another string, or add characters to the name of the flow. Optionally, deactivate or delete the flow. |
|
|
|
Input or output fields couldn't be found for this flow during deployment. File a support ticket and include the reference code that is associated with this error. |
|
|
|
A label for an option field can contain letters, numbers, hyphens, underscores, and spaces only. Leading or trailing spaces are prohibited. Remove unsupported characters from the label for the option field. |
|
|
|
In the IO dialog, the helper flow built to retrieve data for option fields is missing or inactive. Make sure you've selected a helper flow for your dynamic options and that it's activated. |
|
|
|
A helper flow used to create dropdown option fields has a dependency on a result from another dropdown. However, the latter dropdown depends on a result from the first dropdown. Resolve the circular reference. |
|
|
|
In the IO dialog, the helper flow that is built to retrieve data for input fields is missing or inactive. Make sure you've selected a helper flow for your dynamic input fields and that it's activated. |
|
|
|
A label for an input field can contain letters, numbers, hyphens, underscores, and spaces only. Leading or trailing spaces are prohibited. Remove unsupported characters from the label for the input field. |
|
|
|
In the IO dialog, the helper flow that is built to retrieve data for output fields is missing or inactive. Make sure you've selected a helper flow for your dynamic output fields and that it's activated. |
|
|
|
A label for an output field can contain letters, numbers, hyphens, underscores, and spaces only. Leading or trailing spaces are prohibited. Remove unsupported characters from the label for the output field. |
|
|
|
A function card (such as Call Flow or For Each) is unable to call a flow. The called flow may be inactive or missing. Make sure you've selected a flow and that it's activated. |
|
|
|
A connector can't pass validation or be deployed successfully unless it contains at least one active action flow. Action flows begin with a Connector action card. Make sure that your connector project contains at least one active action flow, or create and activate an action flow to deploy your connector. |
|
|
|
A label for an authentication parameter can contain letters, numbers, hyphens, underscores, and spaces only. Leading or trailing spaces are prohibited. Remove unsupported characters from the label for the authentication parameter. |
|
|
|
In the Authentication dialog, the helper flow that is built to return data to the end user is missing or inactive. Make sure that you've selected a helper flow for the Config Values inputs of your connector and that the flow is activated. |
|
|
|
A helper flow that is built to run when an error is encountered is missing or inactive. Make sure that you've selected a helper flow for error handling and that the flow is activated. |
Soft Validations
Soft validations also indicate a failed deployment of a connector. While soft validations don't prevent you from deploying a connector, it's recommended that you address the issues described in any error message returned with your attempted deployment.
|
Reference code |
Validation error |
Description |
|---|---|---|
|
|
|
An action flow previously deployed as part of this connector is now inactive or is no longer part of the project. This change could interrupt any existing flows that use this connector. |
|
|
|
An input field previously deployed as part of this action flow has been removed. This change could interrupt any existing flows that use this connector. |
|
|
|
An output field previously deployed as part of this action flow has been removed. This change could interrupt any existing flows that use this connector. |
|
|
|
A dynamic input field previously deployed as part of this action flow has been removed. This change could interrupt any existing flows that use this connector. |
|
|
|
A dynamic output field previously deployed as part of this action flow has been removed. This change could interrupt any existing flows that use this connector. |
|
|
|
A registration flow wasn't selected as part of your webhook event flow. Many services can register webhooks through an API interface. However, if your service doesn't require registration, then you can ignore this message. |
|
|
|
A deregistration flow wasn't selected as part of your webhook event flow. Many services can deregister webhooks through an API interface. However, if your service doesn't require deregistration, then you can ignore this message. |
|
|
|
Add the Flow Control Cursor function card to your flow. |
|
|
|
Map the Cursor output on the Polling Monitor event card to another card in the flow. |
|
|
|
Add at least one group to the Static Output Group pane in the Outputs dialog. |