> For the complete documentation index, see [llms.txt](https://wiki.lucysecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.lucysecurity.com/release-notes/5.7.3.md).

# 5.7.3

## Release Notes

#### March 2026

This patch release focuses on improving stability, usability, and consistency following the changes introduced in version 5.7.

Key fixes and improvements include:

* **One-Shot Rule Scheduling:** Fixed issues that allowed invalid configurations and simplified the handling of date fields.
* **Awareness Scenario Naming:** Scenarios can now be renamed independently from their templates, providing greater flexibility when managing campaigns.
* **SSO Improvements:** Resolved several issues, including unexpected logouts from the End User Portal and improved support for direct SSO login links.
* **API Documentation:** Corrected a Swagger documentation mismatch related to victim click data.
* **Macro Triggers:** Fixed a bug affecting macro success triggers in mixed scenario templates.
* **UI Fixes:** Addressed minor interface issues, including incorrect display of the template progress bar.

Overall, this patch improves reliability and resolves several edge cases introduced after the 5.7 release.


---

# 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://wiki.lucysecurity.com/release-notes/5.7.3.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.