> For clean Markdown of any page, append .md to the page URL. > For a complete documentation index, see https://docs.itential.com/llms.txt. > For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.itential.com/_mcp/server. # Troubleshoot errors and warnings > Use the Errors and Warnings modal to identify and resolve workflow validation failures that prevent or impact workflow execution. When a workflow is saved, a number of validation checks are run against it to detect issues that may (or will) prevent it from working properly. Workflow validation failures fall into one of two categories: * **Errors**, which prevent the workflow from running. * **Warnings**, which indicate potential issues with the workflow, but allow the workflow to run. The **Errors and Warnings** modal can be used to assist in troubleshooting workflow validation failures. ## View errors and warnings To view any errors or warnings present in a workflow, click the **View Errors and Warnings** button on the canvas title bar. The **Errors and Warnings** modal will open. ![](/_fern-img/3e08344221eeb4926dc110697c01f1d1576cdeaa0b7d2eef433a0dfb629a7f65.webp) From the **Errors and Warnings** modal, you can view all validation failures present in a workflow. The modal can be filtered to show only errors or warnings via the **Errors** and **Warnings** checkboxes, respectively. Validation failures are presented in a table view separated by task. Click on any failure from the table to be redirected to where the failure occurred. ![](/_fern-img/55e3baff6a05a18ebfbd80cd381e91f170d9406764ebe56c105a89cb2db81619.webp) ## Error references The following table provides a reference list of errors that can be found in a workflow. | Draft error | Description | How to fix | | ---------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- | | No config found for adapter `${app}`. | The task adapter is not in the config. | Install the adapter on the current Itential Platform. | | Cannot find match for input `"${leftoverModelInput}"` from model. | Task parameters do not match the parameters on the task model. The task model contains a parameter that is not defined in the task. | Delete and re-add the task on the workflow to save against the correct model inputs. | | Cannot find match for input `"${leftoverTaskInput}"` from task. | Task parameters do not match the parameters on the task model. The task contains a parameter that is not defined in the task model. | Delete and re-add the task on the workflow to save against the correct model inputs. | | Output `${output}` does not match model output `${outputName}`. | Outgoing variable in task does not match the name of the output defined on the model. | Delete and re-add the task on the workflow to save against the correct model output. | | Method not found. | The adapter task method is not defined in the adapter config. | Restart the adapter. If the method is still not found, replace the task with a valid adapter task. | | No applications found. | No applications in the config. | Check that the application is present in the services page and restart the application. | | Package not found. | Package not found in the config. | N/A | | Input `${inputName}` is not a valid name according to platform naming conventions. | A model input of a task does not follow Itential Platform naming conventions. | Fix the invalid name using a valid name. | | Output `${outputName}` is not a valid name according to platform naming conventions. | The model output of a task does not follow Itential Platform naming conventions. | Fix the invalid name using a valid name. | | Referenced job variable `"${varName}"` is not a valid name according to platform naming conventions. | The reference job variable of a task's incoming variable was edited in a way that makes it invalid. | Fix the invalid name using a valid name. | | Outgoing job variable `"${varName}"` is not a valid name according to platform naming conventions. | The outgoing variable of a task was promoted to a job variable and edited in a way that makes it invalid. | Fix the invalid name using a valid name. | | Error job variable `"${varName}"` is not a valid name according to platform naming conventions. | The error variable of a task was promoted to a job variable and edited in a way that makes it invalid. | Fix the invalid name using a valid name. | | Task cannot contain `${state}` standard and revert transitions. | A task contains a revert and standard transition of the same state (success, failure, or error). | Remove either the standard or revert transition with a duplicate state from the invalid task. | | Task must contain only one `${state}` revert transition. | A task contains two revert transitions of the same state (success, failure, or error). | Remove any duplicate state revert transitions from the invalid task. | | Manual tasks require "groups" array to contain at least one active group. | A manual task can have zero groups specified or one group or many active Itential Platform groups. | Either add an active group to the manual task or remove all its groups. | | Manual tasks require "view" key with path to task view. | A manual task does not contain a view, although it is required by all manual tasks. | Provide a valid view in the `pronghorn.json` for the task. | | Invalid transition object requires keys: "type", "state". | The automation contains a transition that is missing the type and/or state properties. | Replace the invalid transition with a valid transition. | | Invalid "from" task is not found in task list. | The automation does not contain the "from" task in the transition. | Replace the invalid transition with a transition that contains a valid "from" task. | | Invalid "to" task is not found in task list. | The automation does not contain the "to" task in the transition. | Replace the invalid transition with a transition that contains a valid "to" task. | | Invalid "type" for transition; must be one of `${types}`. | The transition has an invalid type. | Replace the invalid transition with a valid transition type: "standard" or "revert". | | Invalid "state" for transition; must be one of: `${state}`. | The transition has an invalid state. | Replace the invalid transition with a transition with a valid state of "error", "failure", or "success". | | Transition is part of a cyclic path. | The automation contains standard transitions that create a cycle. | Remove a transition to prevent cyclic paths. | | Revert transitions must be from a future task to a previous task. | The automation contains a revert transition that moves forward in the automation. | Remove the offending revert transition. | | Loop transitions can only exist from loop tasks (i.e. "forEach") to other tasks. | The automation contains a loop transition from a task that is not `forEach`. | Remove the offending loop transition. | | Task cannot be scheduled without at least one enabled run window day. | Run window for a scheduled task is not defined. | Set a run window for the scheduled task. | ## Warning references The following table provides a reference list of warnings that can be found in a workflow. | Warning | Description | How to fix | | -------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- | | Invalid incoming static variable value `${variableName}` is required but no value was provided. | A non-string incoming variable for a task is marked as required, but the field is left empty. | Provide a valid value for the required variable in the invalid task. | | Invalid incoming static variable value `${variableName}` is of type enum but has a non-enumerated value `${variableValue}`. | A static variable is of type enum, but the value input is not of type enum or string. | Provide a valid value for the required variable in the invalid task. | | Invalid incoming static variable value `${variableName}` should be of type `${variableType}` but is of type `${typeof variableValue}`. | The static variable type does not match the type defined on the task. | Provide a value of the correct type for the offending variable in the invalid task. |