Trigger corruption

[Massimo Gassino]

I am using Zabbix 3.2.4 to monitor 670 Host. No problems since 2 year ago installation . Now suddenly we have discovered that triggers table associated with some of the 670 hosts is corrupted and the related action become unpredictable. The triggers are defined in a template and these triggers are still ok. About 10% of host are corrupted.
---------------------
For example :
Original trigger stored into template :
{MyTpl_CLIENTIroc.num[rdpclip.exe].sum(#2)}=0 and {MyTpl_CLIENTI:service_state[WKISaaSUpdate].last(#1)}>0 and
{MyTpl_CLIENTI:service_state[WKISaaSUpdate].last(#2)}>0 and
{MyTpl_CLIENTI:system.uptime.last()}>1200 and
{MyTpl_CLIENTI:system.run[\\saasprodservice\e\temp\testdns.bat {HOSTNAME},wait].str(KO)}=0
and {MyTpl_CLIENTI:system.uptime.nodata(600)}=0

Trigger of BACHETTI host :
{BANCHETTIroc.num[rdpclip.exe].sum(#2)}=0 and {BANCHETTI:service_state[WKISaaSUpdate].last(#1)}>0 and
{BANCHETTI:service_state[WKISaaSUpdate].last(#2)}>0 and
{BANCHETTI:system.uptime.last()}>1200 and
{BANCHETTI:system.run[\\saasprodservice\e\temp\testdns.bat {HOSTNAME},wait].str(KO)}=0
and {7567
-----------
It seems the trigger is truncated .
-----------
How can I restore the correct situation ? Do I need to scan 670 host one by one to check corruption ? Is there any scripts that can help ?
I have experimented that the correct situation can be restored only if I "unlink and clear" the template and relink it again. Unfortunately it seem not possible to do this operation as a mass update.
--------------

Any suggestions ?
Thanks
Massimo