Difference in Discovery Action Behavior Between Zabbix 5.0 and 7.0

[rody]

Hello,
We are using Zabbix discovery actions to detect newly launched servers created by AWS Auto Scaling.
After migrating from Zabbix 5.0 to 7.0, we noticed that a discovery action that used to work correctly no longer triggers. It appears that there is a difference in the behavior of discovery actions between Zabbix 5.0 and 7.0.

---

Environment / Usage

• Detecting newly launched servers via AWS Auto Scaling
• Using Discovery Actions for detection
• Discovery condition is based on SNMP agent checks

---

Observed Behavior

It seems that the handling of “Discovery time” when performing SNMP agent discovery differs between Zabbix 5.0 and Zabbix 7.0.
Regarding the behavior when re‑discovering already discovered devices
(devices shown as grayed out):

• Zabbix 5.0:
  When a discovered device is scanned again, the discovery time is reset.
• Zabbix 7.0:
  When a discovered device is scanned again, the discovery time is not reset.

Because of this difference, discovery actions that worked correctly in Zabbix 5.0 are not triggered in Zabbix 7.0.

---

Questions

We would like to confirm the following points:

• Is this behavior in Zabbix 7.0 an intentional change in specification?
• Is there any configuration option or workaround to reset the discovery time when re‑discovering an already discovered device?
• Are there any known issues, limitations, or similar reports related to this behavior?

Any guidance or insight would be greatly appreciated.
Thank you.

---

If you want, I can also:

• Shorten this for a quick forum post
• Adjust the tone (more formal / more casual)
• Add version numbers, screenshots references, or logs wording

Just tell me