Hello,It looks more like a bug because this behavior appeared for us
after the 6.6.2->6.6.3 update for our customers. Everything continues to
work well as before. However, the logs are polluted and exceptions had
to be made on the SIEM side.Regards,J...
