---
title: "🚀 Software Release Overview: 16.46 🚀"
description: "🛠️ Updates & Improvements 🌱"
canonical_url: "https://support.caremaster.com.au/articles/software-release-overview-1646-0swxsFx4Nz"
md_url: "https://support.caremaster.com.au/articles/software-release-overview-1646-0swxsFx4Nz.md"
---
# 🛠️ Updates & Improvements 🌱


**We are pleased to release several system improvements with this release. Please find below a summary of the latest additions.**


**⌚Daylight Savings affecting worker Availability when rostering supports**

An error was occurring when a worker was being rostered up to their Availability. This was found to be a time displacement based on the seasonal Daylight Savings change and it was adjusted to include the updated times.


⏱️**Notifications not being sent for ‘Trans No Start Notification’ and ‘Trans No End Notification’** 

The ‘Trans No Start Notification’ and ‘Trans No End Notification’ are not being sent for a specific Service Organisation. The cause was identified to be based on a Daylight Savings time issue and was resolved.


📲**Unable to login to the Client App**

Clients were unable to login to the Client App as a microphone permissions setting was not working. This issue had been resolved and the Client App is working again.


⚙️ **Highlight unassigned Supports setting not working on Service Organisation or Participant roster**

The setting 'Highlight unassigned Supports' under Settings > System Settings was only working on the worker and vehicle roster and was NOT working on **Service Organisation** or **Participant** roster. This was fixed and is working as intended.


🛣️ **Kilometres are not being Invoiced**

A fix has been applied for when the Worker App settings ‘Override distance on support/timesheets based on worker app data’ is off and ‘Total Distance Prompt is on’, the worker was not being prompted to add KM’s via the App and the pre added km’s on the web were flowing to the worker timesheet, but not to the customer invoicing. 


🧑‍⚕️Workers using the Worker App were receiving a 500 Server Error when making a change to their Availability. The underlying issue was identified and updated.