I've been using the following regular expression in logrt to specify the log file without any issues for several weeks:

Code:
logrt[C:\Programas\3. Version DEBUG PalStats con Grafico\Logs\Actual\^\d\{4}-\d\{2}-\d\{2}_\d\{2}-\d\{2}-\d\{2}\.log,"ERROR",,,"skip",]
However, today, unexpectedly, I encountered an error with this item stating:

"Cannot compile a regular expression describing filename pattern: PCRE2 does not support \F, \L, \l, \N{name}, \U, or \u, position 39, flags:0x2400".

Enclosing the directory path in quotes does not resolve the issue. I haven't come across any updates that might have impacted this behavior. Does anyone have an idea what could be causing this?

It seems that even if all the "-s" are escaped to "
-s", it still doesn't work: it indicates that regular expressions cannot be used in the path route.

However, if I only escape "
Logs" in the path, the corresponding item in Zabbix transitions to an "enabled" state without showing any errors. However, it fails to capture the expected logs values. 

**

logrt[C:\Programas\3. Version DEBUG PalStats con Grafico\\Logs\Actual\^\d{4}-\d{2}-\d{2}_\d{2}-\d{2}-\d{2}\.log,"ERROR",,,"skip",]

**
It's a bit counterintuitive. It seems that in a minor release, someone wanted to improve the debugger by searching for \F, \L, \l, \N{name}, \U, or \u throughout the entire path, forgetting that regular expressions can only be used in the filename.

Thanks.