---
title: Version 6.4.5
description: "### What's New? ### Bug Fixes #### Visitor Manager - Visitor: badges were printed on two pages. When the translation of the word \"Visitor\" in the badge language was long, the label wrapped onto a second line and the badge…"
url: "https://support.ontimesuite.com/docs/release-notes-otms/version-6-4-5/"
updated: "2026-10-13"
category: Release Notes
---

# Version 6.4.5

### What's New?

### Bug Fixes

#### Visitor Manager

- Visitor: badges were printed on two pages. When the translation of the word "Visitor" in the badge language was long, the label wrapped onto a second line and the badge no longer fitted on one page. Fixed: the label is always printed on a single line, with the font reduced to fit the badge width when needed, so each badge prints on one page.

#### Backend

- **Apache Tomcat upgraded from 10.1.59 to 10.1.61.** This adds the 10.1.60 security fixes, including an Important fix for an HTTP/2 request header mix-up, and the HTTP/2 and TLS stability fixes in 10.1.61. No configuration changes are needed.
- **Better Graph support on EWS-directory domains.** Users’ Graph identities are now filled in when the application starts. This puts them in Internal Graph subscriptions and avoids unreliable lookups by address when their mail address differs from their sign-in name.
- **More robust subscription service.** Errors in one domain’s configuration no longer affect the others. The service now shuts down cleanly during startup and restarts, and waits for migration resyncs to finish before it starts. Repeated or stale notifications now trigger fewer unnecessary full Graph calendar syncs.

### Bug Fixes

#### Desktop

- **Responding to invitations in another user’s calendar failed.** Accepting, tentatively accepting or declining an invitation there could fail when the two users’ domains used different event sync methods. The response is now made on behalf of the calendar owner.
- **UI error when editing recurring all-day events.** The error stopped the edit. These events can now be edited normally.
- **Event view error after accepting an all-day invitation.** Opening the event from the calendar afterwards could break the view. It now opens correctly.
- **Removing an optional attendee from a recurring event wasn’t saved.** The attendee is now removed from all occurrences when the event is updated.

#### Backend

- **Deleting a new recurring meeting failed (Graph).** Deleting all occurrences of a recurring meeting right after creating it, without refreshing first, returned “Internal server error” and left the series in the calendar. The whole series is now deleted.
- **False room conflicts when moving a recurring meeting (Graph).** A meeting could show a conflict with its own occurrences. Real conflicts with modified occurrences are still detected.
- **Couldn’t save changes after accepting a series (Graph event sync).** Attendees who had accepted a whole series couldn’t save changes to it. Changes that don’t involve attendees now save. Unexpected server errors are now logged with a full stack trace.
- **Recurring meetings disappeared from OnTime (Graph event sync).** After attendee actions or an event sync, they could vanish from OnTime even though they were still in Outlook. They’re now kept, and an Event Sync brings back any that are missing.
- **Wrong time or date on all-day events (Graph event sync).** Right after an all-day event was created, edited or accepted, it could show the wrong time or date. It now shows on the correct day, from midnight to midnight, without a refresh.
- **All-day invitations showed on the wrong day.** This happened when the device time zone differed from the OnTime work-hours time zone. It’s fixed, including for recurring invitations.
- **Deleting a recurring meeting sometimes failed.** This happened when it ran at the same time as a user synchronization.
- **Wrong start date or time on new recurring events.** The time zone wasn’t set correctly when the event was created.
- **Internal Server Error on event details.** This happened when details were requested before the event had synced to the OnTime database. The request now uses the caller’s identity where possible, or returns a clear “not found”.
- **Updating a recurring event failed** if the event hadn’t been refreshed first.
- **Switching Events Sync Method (EWS ↔ Graph).** During the resync after a switch, the subscription service could be started by hand. The migration sync and the real-time sync then wrote to the same calendars at once, which caused duplicate-key errors and mailbox throttling. The service now shows as CANNOT_START_YET during the resync and starts on its own when the resync is done. Graph resends any notifications that arrive in the meantime.