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

# v3.44.1

We are happy to announce release v3.44.1 of Elimity Insights, released on 17 April 2026.

## Summary

This section summarizes the most important changes in release v3.44.1.

<details>

<summary>New functionality</summary>

*None*

</details>

<details>

<summary>Bug fixes &#x26; improvements</summary>

* Minor bug fixes & improvements

</details>

<details>

<summary>Deployment changes</summary>

*None*

</details>

## Bug fixes & improvements

### Minor bug fixes & improvements <a href="#h_01js1h4hg2ekpaqj0a5kpn1hc0" id="h_01js1h4hg2ekpaqj0a5kpn1hc0"></a>

This release only includes a few minor bug fixes & improvements:

* Fixed a bug when downloading an Excel file from a stored query.
* Fixed a bug where downloading an Excel file resulted in an error when including 'via' entities.
* Provided additional logging and context for the [NTFS built-in connector](/reference-manual/built-in-connectors/ntfs.md).
* Summaries at the top of entity detail pages now load independently of the data tables further down, which improves responsiveness for customers with large datasets.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.elimity.com/release-notes/v3.44.1.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.