---
title: AI Guarding 2026.5
slug: enterprise/ai-guarding-20265
createdAt: 2026-03-19T15:01:36.601Z
---

This release will be accessible to all customers using the cloud-hosted system on 24-Nov (core) / 1-Dec (edge) during our service maintenance window.

# What’s new?

**Lower GPU load from Personalized AI**
Personalized AI (PAI) now checks each camera once a second, instead of about three times a second. Each camera needs less GPU power as a result.

This also applies to PAI attributes you have already created, including any where you changed the interval yourself. After the update, they all check once a second. You can change the interval again in the Personalized AI tab of the Settings module.

With the slower rate, PAI events can arrive about 1.5–2 seconds later, and objects that are in view for less than about 3 seconds may be missed. If you use PAI on cameras with a lot of activity, check your results after the update. If detection gets worse, contact Irisity Support.

![](https://api.archbee.com/api/optimize/JzHznijrWxPLJLDUaV5A1/uHmjLyAXfKXnIXhyyIj7X_image.png)

![](https://api.archbee.com/api/optimize/JzHznijrWxPLJLDUaV5A1/WGpq_kq9zBoFNXENJmgYm_image.png)

**Clearer setup in the device manager**
&#x20;The “User settings” button is now called “System advanced settings”. This separates device manager configuration from your personal preferences.

![](https://api.archbee.com/api/optimize/JzHznijrWxPLJLDUaV5A1/uZzzrdI9RCVC9Y1kwz9ZI_upload.png)

# What’s improved?

### Security & Compliance

&#x20;This release includes security improvements across the portal and the platform. We will keep releasing security improvements in future updates.

**External API: Clearer response when sign-in is unavailable.**&#x20;

If the authentication service is briefly unavailable, the External API now returns 503 (Service Unavailable) instead of 401 (Unauthorized). Your integration does not need to create a new token or stop retrying during a short outage.

**Stricter check on old-style access tokens.**&#x20;

The platform now rejects old-style (legacy) access tokens that do not have a valid signature. This update will mainly affects older digital I/O gateways. If a device stops connecting after this update, updating the device to a version from 2023 (or newer) should resolve this issue.&#x20;

There are no other changes to API endpoints, the WebSocket connection or authentication in this release.

# What’s fixed?

### Alarms and detection

- Rules set to “But not when: Train” no longer raise alarms while a train is in view.
- Alarm filtering now works when several objects of the same type appear in the same place at the same time.
- New alarms keep appearing in the portal when an alarm comes from an unknown rule type. The unknown rule type should no longer exist after this update.&#x20;
- Notification emails that fail to send are now shown as failed instead of sent.

### Rules and settings

- Searching in the “Detect when” list now returns matching results.
- You can now add a Personalized AI attribute without choosing a default mode. By default, the default mode of the attribute will now be "include".&#x20;
- You can now add an active time to a schedule when your user profile uses the Indian time format, using a 12-hour clock, AM / PM format.&#x20;
- Pressing Cancel in account-level Logical View settings now discards your changes.
- Users with Read and Update permissions can now move cameras and folders.

### Sign-in

- Skipping the authenticator prompt now shows a clear sign-in message instead of a 500 error.
- The recovery code is now readable in all browsers.
- The “session expired” message now appears after an automatic logout.

### Investigation, Monitor and Cases

- Investigation: the progress bar stays visible when you change page or filter.
- Investigation: the search tabs stay visible while results load, and your selected tab is kept.
- Monitor map: the camera pop-up now covers the map correctly.
- Create Case: error messages now line up with their fields.
- Digital I/O: table headers now line up with their columns.

# Known limitations

**Personalized AI attributes created before this update.** The new once-a-second interval only applies to PAI attributes created after the update. Existing attributes keep their current interval, so they don’t get the lower GPU load. If you want an existing attribute to use the new rate, change its interval to 1000 ms in the Personalized AI tab of the Settings module.

**Face recognition (preview) and static watchlists.** After this update, face recognition may not create “person is recognised” events for people in static watchlists. Until this is fixed, do not rely on static watchlists for face recognition. We are investigating. If this affects you, contact Irisity Support with the camera name and the time a person should have been recognised.

**“But not when: Train” on non-standard cameras.** The train filter works only on standard CCTV cameras. It does not work on thermal, fisheye or 360° cameras .

**Imported calendars and anomaly detection.** Calendars imported from an .ics file or a link do not turn anomaly detection on or off. A fix is planned for a later release. Until then, create the calendar’s time frames in the portal instead of importing them.

**Calendars imported from a link.** A calendar imported from a link may not include every event. To avoid this, download the .ics file and import it as a file.

**Closing alarms through External API v2.** If your integration closes alarms through External API v2, the request may return an error and the alarm may be saved with the wrong status. Status values read through API v2 may also be wrong. Until this is fixed, close alarms in the portal. If your integration reads alarm status through API v2, contact Irisity Support.

# Patches & Hotfixes

None to date.

