When a variable is used in a SQL, the variable intersects the message issue.
Steps to reproduce the issue
The problem happens only when we use the variable '&$CLIENT#' in the following SQL statement.
select count(*) from dbo.eh where eh_Client=&$CLIENT# and eh_status=1820 and eh_name='.FRM.RETCODE_ERROR.SCRI'
If you replace the variable '&$CLIENT#' with the actual client number (eg. 100) in the SQLI variable, it works fine.
Select count(*)
from uc4.eh
where eh_Client=100
and eh_status=1820
and eh_name='.FRM.RETCODE_ERROR.SCRI'
Automic Engine 12.3.x
This is a bug and it will be fixed in a future release