Expr Error Codes

Evaluating Expr expressions may produce errors. Normally these errors are shown to the user with a human-readable message. However, in some cases you might need to check for a specific error using the ISERR function.

Error Code	Name	Displayed As	Description	How to Fix
1	Parse Error	???	The expression is invalid. The formula editor should highlight the problematic place with red. If you hover the mouse pointer over the red area, a tooltip with the details of the problem is shown.	Review and edit the expression.
2	Unknown Function	FUNC?	The expression calls a function that is not available or does not exist. This error is also shown if you call a user-defined function, but the variable is actually not of the user function type, for example: `WITH x = 1 : x(1)`.	Review used functions in the expression to see if there are any typos in the names. Check the Expr Function Reference. If you're using user-defined functions, make sure the names you're calling refer to functions.
3	Bad Number of Arguments	ARGS?	A function is used with an incorrect number of arguments.	Review the expression and see if all functions are called with a correct number of arguments. Check the Expr Function Reference.
4	Arithmetic Error	DIV/0	An arithmetic error was encountered. Most often it is division by zero, but it may also be something else, such as passing a non-integer value to a function that expects only an integer.	Review your formula to ensure you're not dividing by zero. (To avoid division by zero, use the IF expression.) If this does not work, try separately calculating parts of the formula to identify the error.
5	Variable Error	VAR!	An attribute that a variable was bound to produced an error.	To fix, review the attributes bound to the expression variables and see why they could have produced an error for the row that shows this error. Try viewing the related attributes in separate (temporary) columns.
6	Function Execution Error	FUNC!	A function suffered an internal error.	Contact your Jira administrator so they can take a look at the log files. Contact Tempo Support if possible. As a workaround, review the latest changes you made to the formula and try to achieve the same some other way.
7	Value Type Error	TYPE?	A value is of the wrong type and could not be converted to the type required by a function. This error happens, for example, if a text value cannot be converted to a number, or if a fractional number is used where an integer is required.	Check the formula and function calls, make sure the values passed to the functions are of expected type. Evaluate parts of the expression to debug.
8	Malformed Regex	REGEX?	A text with invalid regular expression was passed to a matching function.	Check the regular expressions that you use. See Expr Pattern Matching for details.
9	Internal Error	ERROR!	There's an internal problem with Jira or Structure.	Contact your Jira administrator so they can take a look at the log files. Contact Tempo Support if possible.
10	Invalid Value	VALUE!	An invalid value was passed as a function argument. For example, a string that could not be parsed as a date.	Check arguments for the functions that expect specific values.
11	Aggregation Error	AGGR?	The formula contains an unknown aggregate function or an invalid aggregate function modifier.	Check that your aggregate function and modifiers are valid and spelled correctly.
12	Execution Limit	LIMIT!	The formula is too complex or caused deep recursion. This error happens when a formula requires too many calculation steps, or if it contains too many nested function calls.	If the formula is indeed too large, consider breaking it down into multiple parts and calculating each part in a separate column. If the formula does not seem too large, see if it applies a user function to a very large data set. Consider ways to reduce the data set. If the formula is sophisticated, check if there may be endless recursion. Finally, you can contact your Jira administrator and discuss raising the execution limits via Advanced Configuration and Dark Features.
13	Array Too Large	ARRAY!	The array is too large. Structure places a limit on how many values an array may have.	Consider reasons for having so many values in one array. Perhaps you could use an aggregation function instead.