Error Message :
N/A
PromptSets that use a non-existing variable, generate a forced trace. Tasks using such a prompt will hang in a "Resolving Variables".status.
If, for example- Task A contains a promptset that uses a VARA.EXEC as a data reference
- This VARA.EXEC executes task B that gets values from a non-existing VARA (with GET_VAR)
Then upon execution- Task B will fail.
- Task A will remain in "Resolving variables" status.
- A forced trace will be generated by the Automation Engine server.
Investigation
VARA.EXEC.ADDITION executes SCRI.ADDITION with &OPE1# and &VARA# as input values. &OPE1# is set with value '1' and &VARA# with 'VARA.STATIC.OPE', the name of a static variable. However this variable does not exist.<Please see attached file for image>

SCRI.ADDITION uses GET_VAR to read a value from &VARA# (static variable 'VARA.STATIC.OPE'):<Please see attached file for image>

PRPT.ADDITION contains a combo box which uses VARA.EXEC.ADDITION as a data source:<Please see attached file for image>

PRPT.ADDITION is nested in SCRI.PRINT.RESULT:<Please see attached file for image>

Results
Expected: Upon execution of SCRI.PRINT.RESULT, the Automation Engine should return an error message stating that the variable object is missing and cannot be resolved.
Actual: Previewing
VARA.EXEC.ADDITION causes errors, which is the desired behavior:
<Please see attached file for image>

However, when running SCRI.PRINT.RESULT, it stays in 'Resolving variables' status and may not be canceled.<Please see attached file for image>

A forced WP trace is written by the Automation Engine server.