I forgot to indicate that my trigger is configured with "PROBLEM event generation mode" = Multiple as I need a dkistinct trigger for every single value of my item.

As describe in my post to the Zabbix forum, I also tried to configure the following trigger expression (without recovery expression) :

{MyHost:myZabbixTrapperItem.regexp(.*)}=1 and {MyHost:myZabbixTrapperItem.nodata(60)}=0

With this expression, my trigger fires as expected for the first time when the value comes from the zabbix_sender tool.
But the issue is that it then fires again every 30sec (precisely at seconds 0" and 30") until it properly clears after 60sec.
I do see in the zabbix_server.log (DebugLevel=5) that my trigger expression is evaluated every 30sec (precisely at seconds 0" and 30"). I guess this is the consequence of the nodata() function in the expression but this is causing my trigger to be fired 3 times before the nodata(60) returns 1.
Then I'm wondering why the evaluation is scheduled every 30sec. I supposed it would be better if it waits for 60sec, as passed to the function in my example.

I hope it's clear, thanks!

this issue tracker is for bugreports. please see http://zabbix.org/wiki/Getting_help for support options.

this specific issue seems to be a duplicate of ZBXNEXT-3481

I am reporting a bug and it does not look to be the same issue than ZBXNEXT-3481.
I also tried what is described here for "Multiple triggers, one item, keep PROBLEM status until timeout" : https://www.zabbix.org/wiki/Trigger_examples
Both examples result in the same thing, my trigger fires 3 times for any single item value.

Hi richlv.

Could you please confirm what is exactly the fix for ZBXNEXT-3481?
Is the following statement fulfilled with this fix? :

"To build really powerful event management system, we need to get this fact straight: Once you created your event from the trigger - you need to detach it from problem recovery completely and check only recovery expression."

In that case, I confirm it should cover my case.
Many thanks.

the original issue you reported is covered by ZBXNEXT-3481 (which does not change the behaviour, merely documents it).
the issue in your first comment is different, but i am not aware of a nice solution for it either.

Sorry to say, but this is by design. The lack of documentation is supposed to be covered by ZBXNEXT-3481. Closing as Duplicate.

Regarding your first comment, it looks like support request. Please see http://zabbix.org/wiki/Getting_help for available options.