Triggers for LLD with json

[apg]

I have problem with incorrect trigger
We have json, say ,

{"data":[{"name":"N1","check":true,"connect":true,"stream": true}]}

and I parse and make item prototype . All is OK with it. But I'd like, that I see trigger for stream , when it is false only when check is true. What I have: if I write trigger

stream.last()=false and check.last()=false

I see problem , which immediately closed and I can see, that problem duration was 0.

The same is placed, when I make trigger separate trigger

check.last()=false

and make stream.last()=false dependent on check.last()

What's wrong?

[apg]

One more addition. What I see in the message about alert:

Problem: Stream state for N1
Problem started at 00:02:01 on 2020.11.27
Problem name: Stream state for N1
Host: nnn
Severity: Disaster
Operational data: true
Original problem ID: 76123587

at the same time previous message

Problem: Stream state for N1
Problem started at 06:18:01 on 2020.11.27
Problem name: Stream state for N1
Host: nnn
Severity: Disaster
Operational data: false
Original problem ID: 76176693

[apg]

Thank you for reply. For me it's a bug. Do you know, may be there is a discussion, like ZBX..... already opened for this problem?

[cyber]

Trigger recalculation appears every time one of the items receives new value. Even if you get values to both of those items from same json, there is still a minuscule gap between them due to processing. One item gets new value, recalculate and problem appears, second gets new value, new recalculate, problem closes.. duration 0.
I have experienced similar situation with 2 logfile items (logrt.count() ) used in one trigger. Even if in "latest data" it all looks like a same second, in DB it has difference in 0.0000x part of a second... and it was enough to trigger false alarm.

[cyber]

Don't know, I have not searched for bugreport.