{sauvegarde mysql:mysqlbackup.erreur.count(129600)}>0
hi,
i want to check if an item has some data those last 2 days. If i use this kind of trigger it works but the trigger never goes away. It stay even after 10 days without any alert. If i change and add 1 to the delay then it disapear until a next aloert comme up and again it stays.
After 10 days the xxx..count(129600) should be returning 0 so the trigger should disapear but it do not.
If i edit the trigger and do xxx..count(129601) then the trigger is refreshed and disapear from the active trigger list.
I think there is a bug in the trigger system if n> 86400 the trigger does not fade away when it expire. Anyone knows a way to fix this ?
regards,
Ghislain.
hi,
i want to check if an item has some data those last 2 days. If i use this kind of trigger it works but the trigger never goes away. It stay even after 10 days without any alert. If i change and add 1 to the delay then it disapear until a next aloert comme up and again it stays.
After 10 days the xxx..count(129600) should be returning 0 so the trigger should disapear but it do not.
If i edit the trigger and do xxx..count(129601) then the trigger is refreshed and disapear from the active trigger list.
I think there is a bug in the trigger system if n> 86400 the trigger does not fade away when it expire. Anyone knows a way to fix this ?
regards,
Ghislain.
Comment