> 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-december-2024.md). # Improvements and fixes, December 2024 Improvements and bug fixes released in December 2024. *31 December 2024* ## Improved * **Portal:** Improved Segment dropdowns by sorting them alphabetically. * **Editor:** Improved the ability to record Guides on top-layer elements when they present as dropdowns in the underlying application. ## Fixed * **Editor:** Fixed an issue where Tooltips with linked Guides specified to start from a certain step could not be updated and saved if the linked Guide was updated separately. * **Editor:** Fixed an issue where Guides would not end for one customer due to a cookie handling update. * **Assistant:** Fixed an issue where Guides that were started and then either completed or exited would launch again without user input due to cookie duplication. * **Assistant:** Fixed an issue where text formatting did not appear as expected in Userlane due to global styles from the underlying application still being applied. * **Assistant:** Fixed an issue where the Welcome Slide text alignment was changed from center to left. --- # 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-december-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.