> 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-november-2024.md).

# Improvements and fixes, November 2024

Improvements and bug fixes released in November 2024.

*30 November 2024*

## Improved

* **Other:** Implemented a queuing service for running multiple features in parallel (user import/export, language import/export, auto-translation, PDF export, etc.).

## Fixed

* **Editor:** Fixed an issue where the close (X) button was misaligned on enlarged images in Guides and Messages.
* **Editor:** Fixed an issue where the code selector did not accept all CSS syntax.
* **Assistant:** Fixed an issue where Next Button step types were behaving like Left Click step types in a customer environment.
* **Assistant:** Fixed an issue where the scroll position on long texts in Guide steps was maintained when navigating to the next step.
* **Other:** Fixed an issue where users with invalid user sessions could not re-authenticate with Userlane.


---

# 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-november-2024.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.