Werk #22671: REST API: Disabled bulk_outside_timeperiod was stored as enabled
| Component | REST API | ||||
| Title | REST API: Disabled bulk_outside_timeperiod was stored as enabled | ||||
| Date | Nov 12, 2026 | ||||
| Level | Trivial Change | ||||
| Class | Bug Fix | ||||
| Compatibility | Compatible - no manual interaction needed | ||||
| Checkmk versions & editions |
|
A notification rule that was created or edited through the REST API with time period bulking (when_to_bulk set to timeperiod) and bulk_outside_timeperiod disabled was stored with bulking outside of the time period enabled.
The stored bulking parameters had a time horizon of 0 seconds, a maximum bulk size of 0 and no grouping.
As a result, notifications outside of the time period were not sent immediately as single notifications. They were collected and sent as a bulk notification by the next bulk run.
Reading such a rule through the REST API returned bulk_outside_timeperiod as enabled with these values.
Only the response to the creating or editing request showed it as disabled.
The REST API now stores no parameters for bulking outside of the time period if bulk_outside_timeperiod is disabled.
Existing rules are not changed.
An affected rule shows bulk_outside_timeperiod as enabled with a time_horizon of 0 and a max_bulk_size of 0 when read through the REST API.
To correct it, update the rule through the REST API with bulk_outside_timeperiod disabled.
Sending back what the REST API returned for the rule does not correct it.