IRIS+™ 2025.5.1

irisity is always looking for opportunities to provide the best features and improvements for your needs if you want to use the latest updates to the iris+ cloud, we highly recommend you read through our release content updates will be automatically applied to your system according to our policies this release will be accessible to all customers using the cloud hosted system on 21 oct during our service maintenance window this version will update your edge version to v 39 what's improved? general improvements towards the analytics service the analytics service has been updated in this edge version to provide improvements towards detections, including reducing false positives, improving face recognition accuracy, and reducing hardware resource consumption during face detection processing general improvements towards the free text search in investigation we've made adjustments to the models that drive the free text search functionality in iris+ to improve performance and stability, thereby reducing congestion within the underlying data traffic infrastructure better handling of algorithm service crashes and failures improvements were made to the way the system handles responses when crashes or failures happen to the algorithm services this provides additional attempts to bring the system back to normal operations, thereby reducing the chances of algorithms that might be left stalled what's fixed? fixes were applied to issues found in the core for iris+ enterprise accounts users using two factor authentication (2fa) were unable to add an edge device to their account instead of directing the user to the device settings page, they were redirected to the main dashboard of the administrator tab anomaly training was failing to work or produce proper results milestone integration was failing to play a video stream, stuck on buffering users were unable to add unrecognized persons to a watchlist typo was found in the tooltip text of counterflow traffic when adding or editing a rule smoke & fire were generating events outside of the set alarm zone ram consumption in the edge device went beyond 80% threshold, causing crashes to the edge device investigation results went missing from the results view