> 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/2026/improvements-and-fixes-february-2026.md). # Improvements and fixes, February 2026 Improvements and bug fixes released in February 2026. *28 February 2026* ## Improved * **Editor:** Improved keyword search functionality to deliver more accurate and relevant results when searching for content in the Editor. * **Editor:** Looped Tasks now include a cooldown period after completion, preventing duplicate events from being sent repeatedly. * **Editor:** Removed the Alert column from the Tasks and Tags views in the Editor to reduce visual clutter and simplify the interface. ## Fixed * **Portal:** Fixed an issue where Managers were unable to access the Editor when API authentication was enabled for their account. * **Portal:** Fixed an issue where company settings could not be updated in the Portal. * **Portal:** Fixed an issue where Moderators with access to a specific property were unable to access Portal pages as expected. * **Portal:** Fixed an issue where Moderators were unable to access the Segments page. * **Portal:** Fixed an issue where Moderators were unable to download all survey results. * **Portal:** Fixed a minor display issue on the Guide Analytics page list. * **Portal:** Fixed an issue where segment creation and validation were failing when a filter value was set to zero. * **Editor:** Fixed an issue where the Editor would crash when starting a Guide Preview for a language that had not been detected. * **Editor:** Fixed an issue where the title input field in the Editor was broken and could not be edited as expected. * **Editor:** Fixed an issue where Userlane would disappear after canceling a recording and refreshing the page. * **Editor:** Fixed multiple issues related to auto-translation: translations were failing or being overwritten with incorrect language versions for some customers. * **Assistant:** Fixed an issue where the Assistant was opening unexpectedly on clicks in the underlying application. * **Assistant:** Fixed an issue where images in the Assistant were not loading for customers on the US server. * **Assistant:** Fixed an issue where Tooltips were not all appearing on a page when navigating to it. * **Assistant:** Fixed an issue where content creators needed to add multiple user IDs and perform a hard refresh before Tooltips for a specific segment became visible. * **Assistant:** Fixed an issue where the AI Assistant was opening the Guides menu instead of returning to the conversational chat after a Guide was exited before completion. * **Assistant:** Fixed an issue where the Assistant was not showing on the Userlane Portal for some customers. * **Assistant:** Fixed an issue where user attributes were not being listed in the bootstrap as expected. * **Assistant:** Fixed an issue where the left-click automation action was not working correctly for some customer applications. * **Assistant:** Fixed issues related to region settings not being correctly applied when switching between supported regions, ensuring the correct default region is used. * **Other:** Fixed multiple backend stability issues, including errors related to user authentication session handling, foreign key constraint violations, and internal server errors that were impacting reliability. * **Other:** Fixed an issue where removing a company Manager was returning a broken response. * **Other:** Fixed an issue with user verification logic to ensure the process completes correctly. * **Other:** Fixed an issue where JWT-based access to user invitation endpoints was being incorrectly blocked. * **Other:** Fixed an issue where segments were intermittently returning a 409 conflict error. --- # 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/2026/improvements-and-fixes-february-2026.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.