How to manage order validation for scheduled maintenance state transitions #480

Closed
opened 2026-04-05 16:20:00 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @luisxkimo on 5/20/2025

Hi,

I've checked that new restriction on schedule maintenance states transitions was implemented with commit feat: Implement order validation for incident and scheduled maintenance state transitions.

This breaks our workflow implementation with scheduled maintenance periods. We use that periods to start/stop maintenance periods "on-demand", changing the status and the startAt and endsAt properties in the already existing scheduled maintenance instances.

Now, its seems that once the schedule maintenance period reach end/completed status, its not possible to back to start again same instance.

Which is the recommended approach for the described use case? we need to create everytime a new scheduled maintenance period, with same configurations (labels, monitor affected, etc)?

*Originally created by @luisxkimo on 5/20/2025* Hi, I've checked that new restriction on schedule maintenance states transitions was implemented with commit `feat: Implement order validation for incident and scheduled maintenance state transitions`. This breaks our workflow implementation with scheduled maintenance periods. We use that periods to start/stop maintenance periods "on-demand", changing the status and the _startAt_ and _endsAt_ properties in the already existing scheduled maintenance instances. Now, its seems that once the schedule maintenance period reach end/completed status, its not possible to back to start again same instance. Which is the recommended approach for the described use case? we need to create everytime a new scheduled maintenance period, with same configurations (labels, monitor affected, etc)?
Sign in to join this conversation.
No Label
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/oneuptime#480