Steps to reproduce:

What I think happens is dependent items can run on preprocessed (dependent) items before. preprocessing is complete Perhaps because the history cache is being populated too early? The same goes for triggers.

This leads to a miss-match between what is in the database (the correct value) and what is in the history cache.

So far I have only seen this on preprocessed dependent items that use a regex step. So this may be a factor.

Template is attached for your reference.

Attached is a template that represents a simpler example of this issue than the full kuberentes template (which also shows a similar issue)

This relates to 

1. ZBX-21933

Or at-least I think it's the same issue.

Unforturtunately this is a racey issue thats very hard to make happen on demand, and hence very hard to gather data on.

Result:
**

See problem generated.

Expected:
No trigger