Dynamic Input SQL Error handling

[Subhadeep2707]

I have a Batch macro where I am reading SQL queries and executing the queries within a Dynamic Input tool, among other things. For a few cases, I am getting an error like - "Dynamic Input (3) Error SQLPrepare: [Teradata][ODBC Teradata Driver][Teradata Database](-3807)"

This error is okay. I want to handle these errors so that this SQL query output is skipped and the next input is processed. I don't want to do a record count check as a SQL query output may have 0 records, and it is different from not returning any records because of error. 

Also, is there any way to catch this error in a tool instead of just seeing it in the log? Thanks in advance.

[apathetichell]

So the tool has a sql error and just keeps going??? swap to dynamic input in-db because if it errors out --- the workflow will crash vs giving you 0 records. as you noted ---- 0 records is not the same as a sql error.

[Subhadeep2707]

So I have a list of SQLs in an Excel and the Dynamic Input is supposed to run each and store output in a different Excel. If a SQL is failing, it is showing the error and then moving on to the next SQL. Please see below for screenshot. I want to handle these errors in a better way. I have no issues with the workflow going on.

[Subhadeep2707]

Can anyone help with any suggestion on this?