Inventory Limit Reached AIS notification error

[Hecklezz]

Environment

Second Life Release 26.1.1.23806384790 (64bit)

Rest of Environment-

Release Notes

CPU: Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (3600.03 MHz)
Memory: 16302 MB
OS Version: Microsoft Windows 10 64-bit (Build 19045.7058)
Graphics Card Vendor: NVIDIA Corporation
Graphics Card: NVIDIA GeForce RTX 2080/PCIe/SSE2

Windows Graphics Driver Version: 32.0.15.8115
OpenGL Version: 4.6.0 NVIDIA 581.15

Window size: 1276x911
Font Size Adjustment: 96pt
UI Scaling: 1
Draw distance: 128m
Bandwidth: 10000kbit/s
LOD factor: 1.5
Render quality: 4
Texture memory: 8192MB
Disk cache: Max size 11468.8 MB (8.6% used)

J2C Decoder Version: KDU v8.4.1
Audio Driver Version: OpenAL, version 1.1 ALSOFT 1.24.2 / OpenAL Community / OpenAL Soft: OpenAL Soft
Dullahan: 1.24.0.202510081738
CEF: 139.0.40+g465474a+chromium-139.0.7258.139
Chromium: 139.0.7258.139
LibVLC Version: 3.0.21
Voice Server Version:

April 17 2026 03:14:52

Description

PR with potential fix: #5708

If your inventory is abnormally large and flat enough to receive the InventoryLimitReachedAISAlert notification, if the viewer then tries to notify you a following time with InventoryLimitReachedAIS, it errors saying the notification doesn't exist.

Expected:
Both notifications work and exist

Reproduction steps

1. Be on an account with an abnormally large and flat inventory
2. Receive theInventoryLimitReachedAISAlert alert
3. Receive the notification a second time and observe the notification error saying InventoryLimitReachedAIS doesn't exist

---

This repo is using Opire - what does it mean? 👇

💵 Everyone can add rewards for this issue commenting /reward 100 (replace 100 with the amount).
🕵️‍♂️ If someone starts working on this issue to earn the rewards, they can comment /try to let everyone know!
🙌 And when they open the PR, they can comment /claim #5707 either in the PR description or in a PR's comment.

🪙 Also, everyone can tip any user commenting /tip 20 @Hecklezz (replace 20 with the amount, and @Hecklezz with the user to tip).

📖 If you want to learn more, check out our documentation.

[Hecklezz]

It was indeed a duplicate at #426, but current develop doesn't have this notification at all.
So this revert is correct.

You are indeed right @marchcat, so I'm guessing the issue came about during a merge at some point where the duplicate had already been removed and then ended up removing the notification a second time.