Database 3130 Error - On rare occasions, connection between the Teradata database and the product times-out with a 3130 error code. If this occurs, simply re-start the module in question.
Variable Names - Use of variable names is case sensitive (e.g., 'Fees' is different than 'fees'). Incorrect use of variable substitution (where the case in the substitution doesn't match the csae of the variable name) in the action clauses may cause the run-time to hang in execution. You can determine if this has happened by starting Task Manager and looking for multiple instances of "Interpreter.exe" consuming large portions of the CPU. If this occurs, terminate the Interpreter.exe processes, re-start the run-time module, and change the variable names to match the proper case.
Clean-up Executions/Errors - In the Admin module, a provision on the Tools menu allows you to clean-up prior 'execution' or 'error' entries that are displayed on the Executions and Errors tabs. In order to select the items to be cleaned-up, you must be on the Applications tab to select the Application for which the clean-up is to occur.
Calculation of Metrics - In the Dashboard display of the Admin module, the calculations for max, min, and averages are across the entire specified period. The calculations may appear to be incorrect as a result.
Join text window - In the Design Studio, it is possible to automatically construct "joins" whenever two or more tables are involved in a rule condition. The text field for the SQL Join may be updated by double-clicking in the field. The text field is not automatically updated.
SQL Error Codes - In the Admin module, errors are reported on the Errors-Tab whenever a Spotlight Application encounters an error. At present the SQL error code returned by Teradata is not shown in the error description field.
