Steps to reproduce:

1. Import the following template (template name = Nested LLD template): zbx_export_templates (2).yaml
2. Open the templates discovery rule "Root level LLD", notice, that "Delete lost resources" is set to 1h (1 hour) and "Disable lost resourses" is set to "Immediately"
3. Import the following host (host name = test): zbx_export_hosts (4).yaml, notice that previously imported template is linked to the host
4. Send the following value to LLD rule with key "trap":

   ./bin/zabbix_sender -z 127.0.0.1 -s test -k trap -o '\{"data":[\{"level_0":"01"}]}'
   

5. Observe that a host "Root level LLD: Root level Host prototype 01" is created in status "Enabled"
6. Wait for 1 hour and a couple of minutes
7. Send a different value to value to LLD rule with key "trap":

   ./bin/zabbix_sender -z 127.0.0.1 -s test -k trap -o '\{"data":[\{"level_0":"02"}]}'
   

8. Observe that the host "Root level LLD: Root level Host prototype 01" is deleted and a new host "Root level LLD: Root level Host prototype 02" is created

Result: a no longer discovered host is deleted, even though it wasn't even marked for deletion. See example: example1.mp4
In the example video the other value was sent right after the first one, and after an hour a third value was sent; it's not necessary to reproduce the bug but visualizes that only a no longer discovered, disabled host was supposed to be deleted (see it's info icons' text))

Expected: no longer discovered host is disabled and marked for deletion after 1 hour, it should not be deleted straight away.

Same issue is in other discovered elements - items, triggers, graphs, host prototypes.