KB-1794 "Details: ERROR:EVAL:@reason=index" error thrown when using escalations, timers, and exception flows

Rebecca Jonas — Tue, 17 Dec 2019 19:41:31 GMT

Current Revision posted to Appian Knowledge Base by Rebecca Jonas on 12/17/2019 7:41:31 PM

Symptoms

Events, such as escalations, timers, and exception flows, relying on valid expressions throw an error when activated:

There is a problem with the process "Error on Timer"
Problem: An invalid expression has been encountered.

Details: ERROR:EVAL:@reason=index

Recommended Action: Check the expression including any function requirements and resume.

Priority of this problem: High Priority

Cause

This error occurs when events are configured using expressions that pass in arguments by keyword, for example:

rule!exampleRule(
 time: now(),
 timezone: "EST"
)

As mentioned in the Appian Expressions Documentation, events do not support passing arguments by keyword.

Action

Pass in the arguments by position instead, for example:

rule!exampleRule(
 now(),
 "EST"
)

Affected Versions

This article applies to all versions of Appian.

Last reviewed: December 2019

Tags: known issues, expression rules, applications, process modeler, engines, process models, application design, processes, open issues, open use cases

KB-1794 Timer Event throws "ERROR:EVAL:@reason=index" error

Rebecca Jonas — Tue, 17 Dec 2019 19:41:16 GMT

Revision 5 posted to Appian Knowledge Base by Rebecca Jonas on 12/17/2019 7:41:16 PM

Symptoms

Events, such as escalations, timers, and exception flows, relying on valid expressions throw an error when activated:

There is a problem with the process "Error on Timer"
Problem: An invalid expression has been encountered.

Details: ERROR:EVAL:@reason=index

Recommended Action: Check the expression including any function requirements and resume.

Priority of this problem: High Priority

Cause

This error occurs when events are configured using expressions that pass in arguments by keyword, for example:

rule!exampleRule(
 time: now(),
 timezone: "EST"
)

As mentioned in the Appian Expressions Documentation, events do not support passing arguments by keyword.

Action

Pass in the arguments by position instead, for example:

rule!exampleRule(
 now(),
 "EST"
)

Affected Versions

This article applies to all versions of Appian.

Last reviewed: December 2019

Tags: known issues, expression rules, applications, process modeler, engines, process models, application design, processes, open issues, open use cases

KB-1794 Timer Event throws "ERROR:EVAL:@reason=index" error

Jordan Horwat — Fri, 16 Nov 2018 17:26:33 GMT

Revision 4 posted to Appian Knowledge Base by Jordan Horwat on 11/16/2018 5:26:33 PM

Symptoms

A Timer Event with a valid expression-based delay throws an error when activated:

There is a problem with the process "Error on Timer"
Problem: An invalid expression has been encountered.

Details: ERROR:EVAL:@reason=index

Recommended Action: Check the expression including any function requirements and resume.

Priority of this problem: High Priority

Cause

This error occurs when keywords are used to pass in parameters to the expression used to specify the timer delay, for example:

rule!exampleRule(
 time: now(),
 timezone: "EST"
)

Timer event delays not supporting keyword parameters is a known limitation of the Appian product.

Action

Remove the keywords from the parameters passed into the timer delay expression, for example:

rule!exampleRule(
 now(),
 "EST"
)

Affected Versions

This article applies to all versions of Appian.

Last reviewed: November 2018

Tags: known issues, expression rules, applications, process modeler, engines, process models, processes, open use cases

KB-1794 Timer Event throws "ERROR:EVAL:@reason=index" error

Jordan Horwat — Fri, 16 Nov 2018 12:26:33 GMT

Revision 3 posted to Appian Knowledge Base by Jordan Horwat on 11/16/2018 12:26:33 PM

Symptoms

A Timer Event with a valid expression-based delay throws an error when activated:

There is a problem with the process "Error on Timer"
Problem: An invalid expression has been encountered.

Details: ERROR:EVAL:@reason=index

Recommended Action: Check the expression including any function requirements and resume.

Priority of this problem: High Priority

Cause

This error occurs when keywords are used to pass in parameters to the expression used to specify the timer delay, for example:

rule!exampleRule(
 time: now(),
 timezone: "EST"
)

Timer event delays not supporting keyword parameters is a known limitation of the Appian product.

Action

Remove the keywords from the parameters passed into the timer delay expression, for example:

rule!exampleRule(
 now(),
 "EST"
)

Affected Versions

This article applies to all versions of Appian.

Last reviewed: November 2018

Tags: known issues, expression rules, applications, process modeler, engines, process models, processes, open use cases

KB-XXXX Timer Event throws error "ERROR:EVAL:@reason=index"

Jussi Lundstedt — Thu, 15 Nov 2018 13:45:18 GMT

Revision 1 posted to Appian Knowledge Base by Jussi Lundstedt on 11/15/2018 1:45:18 PM

Symptoms

A Timer Event with a valid expression-based delay throws an error when activated:

There is a problem with the process "Error on Timer"
Problem: An invalid expression has been encountered.

Details: ERROR:EVAL:@reason=index

Recommended Action: Check the expression including any function requirements and resume.

Priority of this problem: High Priority

Cause

This error occurs when keywords are used to pass in parameters to the expression used to specify the timer delay, for example:

rule!exampleRule(
 time: now(),
 timezone: "EST"
)

Timer event delays not supporting keyword parameters is a known limitation of the Appian product.

Action

Remove the keywords from the parameters passed into the timer delay expression, for example:

rule!exampleRule(
 now(),
 "EST"
)

Affected Versions

This article applies to all versions of Appian.

Last reviewed: November 2018

Tags: known issues, expression rules, applications, process modeler, engines, process models, processes, open use cases

KB-XXXX Timer Event throws "ERROR:EVAL:@reason=index" error

Jussi Lundstedt — Thu, 15 Nov 2018 08:45:47 GMT

Revision 2 posted to Appian Knowledge Base by Jussi Lundstedt on 11/15/2018 8:45:47 AM

Symptoms

A Timer Event with a valid expression-based delay throws an error when activated:

There is a problem with the process "Error on Timer"
Problem: An invalid expression has been encountered.

Details: ERROR:EVAL:@reason=index

Recommended Action: Check the expression including any function requirements and resume.

Priority of this problem: High Priority

Cause

This error occurs when keywords are used to pass in parameters to the expression used to specify the timer delay, for example:

rule!exampleRule(
 time: now(),
 timezone: "EST"
)

Timer event delays not supporting keyword parameters is a known limitation of the Appian product.

Action

Remove the keywords from the parameters passed into the timer delay expression, for example:

rule!exampleRule(
 now(),
 "EST"
)

Affected Versions

This article applies to all versions of Appian.

Last reviewed: November 2018

Tags: known issues, expression rules, applications, process modeler, engines, process models, processes, open use cases