Zabbix Server version 5.0.16

While creating a template with multiple event generation mode trigger, our user ran into an issue where the trigger is creating non-legitimate, duplicate problems.

The template follows a master-dependent item structure, having the master item collect XML data via external check, then distribute relevant information between dependent items. The collected data can contain information about multiple interfaces and their components. But, each time XML data is received, it is received about 1 interface and 1 component, one data collection instance can not have information about multiple interfaces/components. Data collection happens every 30 seconds.
Each interface has multiple components, but for this issue we are concerned with 2 components - GPON and XGS. In the end, multiple interfaces and multiple components can report to the same trigger, hence the need for multiple event generation mode.
The XML data that is received contains problem/problem resolve information for 1 interface and 1 component, therefore opening multiple problems is not the expected behaviour, but that is the case nonetheless.

The triggers, which are problematic, look like this:

And here is the issue:

After sending the two XML data blocks that are attached to this issue, data-1.xml and data-2.xml, only two issues should be raised - One for GPON, one for XGS component.
GPON component event has an associated ID - "ywu0fpEB0db_Z9VZWj7Q"
XGS component event has an associated ID - "zAu0fpEB0db_Z9VZWz40"
However, some problems for XGS component have "ywu..." associated ID. This should not be possible with how data is received, and how triggers are set up.
Additionally, due to wrong IDs for problems, recovery events are unable to close the problem, when the issue has been resolved.

To reproduce:
1. Use attached template
2. Convert master item "amqp-get" to some other item (I converted to vfs.file.contents item that reads xml data, instead of external check collecting the data)
3. Allow master item to read data-1.xml, and afterwards data-2.xml
After these steps, you will see the issue reproduced in the problems page.
template-1.xml data-2.xml data-1.xml