[ZBX-24430] Discovery item reports: Cannot update item: Invalid flexible interval "0" Created: 2024 May 02  Updated: 2024 May 06

Status: Confirmed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: None
Fix Version/s: None

Type: Problem report Priority: Trivial
Reporter: Andrey Assignee: Zabbix Development Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

zabbix_server (Zabbix) 6.4.10
Revision 4da16fb82f5 13 December 2023, compilation time: Dec 13 2023 10:03:43

Attachments: PNG File image-2024-05-02-06-24-02-895.png     PNG File image-2024-05-02-06-25-38-959.png    

 Description   

The idea of this item prototype template is to create item that preforms check once per month., but the discovery item cannot create items by such prototype with flexible intervals where interval time = 0. Instead it reports `Cannot update item: Invalid flexible interval "0".` when according to docs it should able to do so: "If the flexible interval is set to '0', the item is not polled during the flexible interval period and resumes polling according to the default Update interval once the period is over."

 Comments   
Comment by Edgars Melveris [ 2024 May 03 ]

Hello!
Why do you need the flexible interval 0, when the update interval is already 0?

Comment by Andrey [ 2024 May 04 ]

Because my goal is to "invert" interval period meaning (i.e. to disable checks during this interval) and this is the way that described in the documentation - here it says: "If the flexible interval is set to '0', the item is not polled during the flexible interval period".
Of course it could be solely a documentation mistake but according to my tests a static item with such settings can be created without errors. The error arises only in conjunction with discovery mechanism, when an item should be created by template so I think that this could be a bug in the discovery system.

Generated at Sat Jun 07 11:31:04 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.