Naming Errors
These errors are typically caused by invalid, duplicate, or reserved names for variables and inputs.
Error 149 — Unexpected token
This error occurs when a reserved or not-allowed name is used for a variable or input. The following names are not permitted:
float
bool
double
string
Resolution: Rename the variable or input using a unique name that is not a system keyword.
Error 196 — Identifier expected
This error appears when the system expects a valid variable or input name, but none is provided or the name is invalid.
Resolution: Ensure all required name fields contain valid identifiers and are not left empty.
Error 256 — Undeclared identifier
This error indicates that a variable or input is being used but has not been defined, or its name no longer matches the defined item.
Common causes include:
Using a variable or input that was never created
Renaming an item in the Inputs & Variables tab without updating its references in blocks
Resolution: Verify that the variable or input exists and that the same name is used consistently throughout the project.
Error 125 — Variable already defined
This error occurs when a variable is defined more than once, for example in multiple Modify Variable or Formula blocks.
Resolution: Ensure each variable is defined only once or reused appropriately.
Error 129 — Struct member "…" already defined
Error 410 — Ambiguous access, can be one of
These errors occur when multiple variables or inputs share the same name, making it unclear which one should be used.
Resolution: Assign unique names to all variables and inputs.
Syntax and Formatting Errors
These errors result from invalid characters or incorrect formatting in inputs or variables.
Error 154 — Semicolon expected
Error 177 — I-value required
These errors commonly occur when disallowed characters (such as a hyphen -) are used in variable or input names.
Resolution: Remove special characters and use only supported naming conventions.
Data Type and Value Errors
These errors occur when values do not match the expected data type or when required fields are incomplete.
Failed to parse value "…" of type Double
This error appears when a text value or an incorrect data type is entered into a field that requires a numeric value.
Resolution: Enter a valid number and ensure the correct data type is used.
Could not parse value of variable "…"
This error occurs when an input or variable in the Inputs & Variables section is empty or contains an invalid value.
Resolution: Confirm that all variables and inputs are properly defined and contain valid values.
Block Configuration Errors
These issues arise from incomplete or improperly configured blocks.
Empty Formula or Modify Variable block
Errors may occur if:
No variable is selected to be modified
No formula or outcome is defined
Resolution: Select the appropriate variable and provide the required formula or value.
Variable to be changed is not selected
This occurs when a Modify Variable block does not specify which variable should be updated.
Resolution: Choose the correct variable in the block settings.
Preventing Errors
To avoid common errors:
Use unique, descriptive names for all variables and inputs
Avoid reserved keywords and special characters
Keep names consistent across all blocks
Ensure all required fields and blocks are fully configured
Verify that values match the expected data types
If you encounter an error not listed here, review the highlighted block referenced in the error message, as it will indicate where the issue originates. If you are still experiencing issues with an error not listed here, please contact us.