> For the complete documentation index, see [llms.txt](https://docs.userlane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.userlane.com/changelog/2024/improvements-and-fixes-september-2024.md). # Improvements and fixes, September 2024 Improvements and bug fixes released in September 2024. *30 September 2024* ## Improved * **Portal:** Aligned user calculations on the Retention page to be consistent with the Adoption and Engagement pages in HEART. * **Editor:** Added support for top-layer elements in Guides so that Guide steps can be recorded on these elements. * **Other:** Improved error handling during the authentication process when Userlane receives the user's ID instead of the email address from the Identity Provider. ## Fixed * **Portal:** Fixed an issue where deleted segments were still being shown in the usage section for Attributes. * **Editor:** Fixed an issue where Tooltip icons bounced on scroll for Tooltips created in tables. * **Editor:** Fixed an issue where searching for and selecting a Segment to apply to a Tooltip or Tag caused the Editor to close. * **Editor:** Fixed an issue where the Editor closed when a customer was trying to edit the name of Tags. * **Editor:** Fixed an issue where the userlane-context cookie was being saved at both the subdomain and domain level, causing Guides to re-trigger upon page reload. * **Other:** Fixed an issue that caused the Browser Extension to not fetch the latest SSO configuration if the integrity token contained certain special characters. --- # 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://docs.userlane.com/changelog/2024/improvements-and-fixes-september-2024.md?ask=&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.