This release makes printing more dependable and calendar changes easier to follow: administrators can now set up a primary print client alongside one or more backup print clients, so a print job automatically moves to the first available Windows queue whenever the primary one is closed, offline, or missing, removing the need for someone to notice the problem and step in manually; at the same time, anyone working with recurring calendar events gets a clear confirmation when a schedule change has been validated by the owner module, and a plain message pointing them to the owner module whenever a direct reschedule isn't possible, so nothing is left ambiguous.

Automatic failover between print clients

Administrators can now configure a primary print client plus one or more backup print clients, arranged in a clear failover order. If the primary client's Windows queue is closed, offline, or can't be found, the print job automatically moves to the next backup client with a working queue, so operations don't stall and nobody has to notice a printer problem before it's fixed.

  • Set up a primary print client and one or more backup print clients, organized in a clear failover order.
  • Print jobs automatically move to the next available client if the primary Windows queue is closed, offline, or missing.
  • Each print client requires a valid Print Client ID (UUID) and the exact Windows queue name, with no leading or trailing spaces.
  • Older printer attribute fields (Type, Paper size, Colour capable, Duplex capable, Duplex by default) have been removed from the settings screen, simplifying configuration.

Clearer status messages for recurring calendar events

When you change the schedule of a recurring event, the calendar now shows a clear confirmation that the change has been validated by the owner module while synchronization completes. If a direct reschedule isn't available, or the event owner isn't reachable, a specific message tells you to modify the recurrence in the owner module instead.

  • Get a clear confirmation when a recurring event's schedule change has been validated by the owner module during synchronization.
  • See an explicit message when rescheduling isn't available or when the event owner isn't available.
  • Know exactly when to switch to the owner module to modify the recurrence and complete the change.

01

What changes for you

If you manage print configuration, you can now set up a chain of print clients: one primary and one or more backups. If the primary Windows queue is closed, offline, or missing, the print job automatically moves to the first available client in that chain, without anyone needing to spot the problem and step in.

If you work with recurring calendar events, you won't be left guessing about a silent change or an unclear error. The system confirms when a schedule change has been validated by the owner module, or tells you precisely where to go when a direct reschedule isn't possible.

02

Why it matters

A print outage at the wrong moment can stop a whole operational process, from a warehouse floor to a back office. Automatic failover reduces that risk by having a backup route ready in advance, so work continues without delays or a call to support.

Clear calendar messaging removes doubt about what actually happened to a recurring event. Knowing for certain whether a change went through, or exactly where to act if it didn't, saves time and avoids scheduling mistakes.