Docs
Scheduled event triggers
April 2, 2026
Event triggers evaluate conditions based on incoming measurements. But what happens when measurements stop arriving altogether?
Until now, detecting an unchanged or stale state required other measurements from the same subject to keep advancing time. With the new Advance time periodically setting, currently in beta, event triggers can evaluate on a schedule even when no new data comes in at all.
You can, for example, trigger an event when:
- A sensor hasn’t reported in over an hour
- A machine has remained idle for too long
- A valve has stayed open when it shouldn’t have
These scenarios were previously achievable using simulated metrics as a workaround. We recommend migrating away from that approach. Simulated metrics are planned for deprecation.
Open the event trigger edit page and click ‘Show advanced settings’ at the bottom to find the new setting. For more details, visit the docs.
If other measurements are arriving for a subject, we recommend to consider the Advance time for other new measurements setting as well. This lets you distinguish between a truly stale condition and a case where the sensor itself has stopped reporting, which is an important difference when, for example, a valve appears to remain open simply because the device went offline. For more guidance on which setting to use when, see the docs.
Improvements
- When showing measurements on a map, you can now reverse the bounds to influence what gets drawn on top
- Browser tab titles show what specific page you are on in the web app
- Improve the editing experience of passwords and MFA settings
- Support cloning roles
Fixes
- Fix visualization of errors when applying changes from another environment
- Fix issue where grid rows cannot be expanded in Firefox
- Fix error message for NaN or infinite values when setting properties in actions