Log file triggers on old entry

Hi Team,

Hoping you can help me find the source of this issue. The log file monitor triggers on already detected entries.

We have it set to run every hour, but we were still receiving the alert 4 hours after the last entry matching.

Here is the set-up Match: "FATAL ERROR in SQL call"

501 matches have been found in file \xxx.log:

r
11-12-2017 12:00:20.070 [176040746, 24215.000,123047936,2950147157]: sql_exec_direct_internal:SQLExecDirect: FATAL ERROR in SQL call
SQL State: 08S02, SQL Code: -1, Message: [Microsoft][SQL Server Native Client 11.0]SMux Provider: Physical connection is not usable [xFFFFFFFF].
SQL State: 08S02, SQL Code: -1, Message: [Microsoft][SQL Server Native Client 11.0]Unable to open a logical session
11-12-2017 12:00:20.070 [176040746, 24215.000,123047936,2950147176]: sql_fetch_internal: FATAL ERROR in SQL call

11-12-2017 12:00:20.070 [176040746, 24215.000,123047936,2950147157]: sql_exec_direct_internal:SQLExecDirect: FATAL ERROR in SQL call
SQL State: 08S02, SQL Code: -1, Message: [Microsoft][SQL Server Native Client 11.0]SMux Provider: Physical connection is not usable [xFFFFFFFF].
SQL State: 08S02, SQL Code: -1, Message: [Microsoft][SQL Server Native Client 11.0]Unable to open a logical session
11-12-2017 12:00:20.070 [176040746, 24215.000,123047936,2950147176]: sql_fetch_internal: FATAL ERROR in SQL call
SQL State: HY010, SQL Code: 0, Message: [Microsoft][ODBC Driver Manager] Function sequence error
11-12-2017 12:00:20.070 [176040748, 24215.000,123047936,2950147547]: sql_exec_direct_internal:SQLExecDirect: FATAL ERROR in SQL call
SQL State: 08S02, SQL Code: -1, Message: [Microsoft][SQL Server Native Client 11.0]SMux Provider: Physical connection is not usable [xFFFFFFFF].