What’s New?
Backend
- Added an extra check when the background sync detects a deleted event with a catering order, to ensure the event was actually deleted and not temporarily unavailable due to Microsoft throttling.
- Fixed an issue where administrators could start manual subscriptions during an EWS-to-Graph migration, which could cause data corruption.
- Updated Apache Tomcat to 10.1.60, including the latest Tomcat Native update, TLS and RewriteValve improvements, and improved WebSocket handling.
Bug Fixes
Visitor Manager
- Improved visitor badges to display long first and last names by reducing the font size when necessary, instead of truncating the names prematurely.
Backend
- Fixed an issue that could cause event data to become corrupted when Microsoft throttled requests for additional event details. This could, for example, affect author permissions on recurring events.
- Fixed an issue that could cause events to become disconnected from their catering orders when switching between EWS and Graph event sync methods.
- Fixed an issue where an empty Graph sync could incorrectly remove a user’s existing events. OnTime now verifies that the calendar is actually empty before applying the sync results.
- Fixed an issue where creating an event could trigger a full sync because Microsoft had not yet made the event fully available.
- Fixed an issue where opening a Teams meeting could freeze the application on large installations. Updating the meeting link could temporarily block other calendar operations. This update is now handled more efficiently to prevent the application from freezing.
- Fixed an issue where some meetings were incorrectly shown as appointments on Graph-synced domains.