Steps to reproduce:

a) On Windows create a text file with encoding UTF-16LE

b) Write multiple lines of content into that log file

c) Have Zabbix Agent 2 present on that Windows device

d) Configure log monitoring for that file using key log["path\to\file.extension",,,,skip] and interval for example 1m

e) Wait for the configuration change to be picked up by the agent

f) Append a single line to that log file

g) Observe that on the first run, last line or multiple lines will be chopped into a larger number of item values (in my case the last value was '?')

h) Update log item key with proper encoding and save (observe that the history of that item is preserved)

i) Append another text to that log file

j) Observe that last value is not getting updated on the next item tick

Expected outcome:
Since the correct encoding was added to item's key afterwards, one would expect that subsequent writes to the log file would periodically produce new last values for that log item.

Actual outcome:
Item seems to become stuck and unable to receive new values.