Product Enhancement Request – Maintenance Event Notifications
Problem / Context
Today, operators are not informed in advance when Tulip maintenance or release activities are executed. This lack of visibility can lead to unexpected interruptions during critical operations and increases the risk of data corruption or incomplete transactions.
Short-term / Temporary Solution (Workaround)
As a temporary mitigation, we plan to implement a declarative maintenance mechanism:
-
Create a dedicated Maintenance Events table to store upcoming maintenance windows.
-
Run an automation that:
-
analyzes upcoming maintenance events,
-
updates a machine attribute with a maintenance notification message.
-
-
In Tulip apps:
-
the machine visual status will change color 15 minutes before maintenance execution (Maintenance mode),
-
once the maintenance end date is reached, the visual state returns to the normal color.
-
This approach will:
-
inform operators in advance,
-
allow them to postpone critical activities if needed,
-
significantly reduce the risk of data corruption caused by maintenance interruptions.
Current Limitation of This Approach
This solution remains fully declarative and does not rely on real-time feedback from Tulip.
There is no reliable confirmation that maintenance has actually started or completed, which limits robustness and trust in the notification.
Product Enhancement Request
To address this gap, we suggest the following native capabilities:
-
Expose scheduled maintenance and release events in a system table (or equivalent), automatically updated by Tulip.
-
Provide a real confirmation signal when:
-
maintenance starts,
-
maintenance is completed (e.g. via a system table update, app info flag, or event trigger).
-
This would enable:
-
reliable pre-maintenance notifications (e.g. 15 minutes before execution),
-
accurate end-of-maintenance confirmation,
-
safer operations and improved data integrity during platform maintenance.