> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/release-notes/web/2025/release-15-28-alarm-notes-for-verifeye.md).

# Release 15.28 - Alarm Notes for VerifEye

June 2, 2025

Updates to the Solink platform in this release include:

***

## Enhancements

* Can now add notes when closing an alarm in the [VerifEye](/docs/protect-your-locations-with-alarms/alarms-with-ai-detection/verifeye-alarm-verification.md) workflow (regardless of whether the response is "Yes" or "No"):

![](https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-d3fd76670fdbcbd2fcf1db963341991c8b006c04%2F7e9980871e189fdc.png?alt=media)

Notes are stored in the alarm event card:

![](https://1562067156-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlMN1EUQcXYfv7FYpGJWR%2Fuploads%2Fgit-blob-c5f10f77fbe79c19238e1a15c0b2c1724a19e640%2F25e151ac1a846fd9.png?alt=media)

***

## Bug Fixes

* Fixed an issue where the VerifEye video player did not display events and/or "people" icons correctly along the timeline.
* Fixed an issue where [Alarm Schedule Exceptions](/docs/protect-your-locations-with-alarms/use-and-configure-alarms/alarm-schedule-exceptions.md) did not save properly in some situations.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.solink.com/docs/release-notes/web/2025/release-15-28-alarm-notes-for-verifeye.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.