v3.46.0
We are happy to announce release v3.46.0 of Elimity Insights, released on 3 August 2026.
Summary
This section summarizes the most important changes in release v3.46.0.
New functionality
Pagination in custom gateway imports
Previously Elimity Insights pulled all entities and relationships in a single request, now it supports splitting the import into multiple pages (only SDK v2):
Retrieval timestamps for reload events
The imports tab of the source detail page now lists additional details about retrieval timestamps for reload events.
Additional endpoint: GET /api/agent/linking-strategies
Elimity Insights now provides a new endpoint to list all linking strategies. The endpoint can be called using an API token.
Evaluation duration added to the stored query page
Visiting a stored query's detail page now shows the elapsed running time of its current execution, making it easy to spot queries that are taking longer than expected.
Timestamps of last evaluation added to the stored query page
Similarly we also added a new 'Last evaluation during import' column to the stored query page.
The same information is also available in the overview table listing all stored queries.
New user account role: storedQueryManager
Elimity Insights now provides a new user account: storedQueryManager . Users who have this role can manage/assign stored queries and scopes of other users.
Global toggle option for 'build history'
Administrators can now use the 'miscellaneous' tab on the 'advanced settings' page to set the default build history behaviour for newly created stored queries. This default has no effect on existing stored queries, and it can still be overridden per query.
When the toggle is on, new stored queries will preserve their history by default. When it is off, new stored queries will not build history by default and their history tab will not be shown. In both cases, the setting can be changed on any individual stored query afterwards.
Toggle option for 'build history' in the stored queries detail page
A toggle option is now available to users with the storedQueryManager role or higher to determine whether Elimity Insights should build history for a specific stored query. The toggle is initially turned on due to the before mentioned global default.
The overview table listing all stored queries now also has a 'build history' column.
Ownership of scopes can now be assigned explicitly
Users with role storedQueryManager or above can now assign ownership of a scope when creating or editing it. Enter the owner's email in the 'Owner' search bar.
Ownership of queries can now be assigned explicitly
Users with role storedQueryManager or above can now assign a different owner to a stored query when creating or editing it, provided the query has no scope.
New 'Download as Excel' button on the stored queries overview page
The stored queries page now offers a 'Download as Excel' button that exports every stored query you have access to, with its status, name, description, owner, scope, latest result count and public flag, to a .xlsx file. The export always covers the complete list, regardless of the filter or page currently shown in the table.
Support for timing out query evaluations during imports
Elimity Insights v3.46.0 also brings support for timing out query evaluations during imports. More specifically, administrators can now enable a specific timeout in the 'miscellaneous' tab on the 'advanced settings' page:
Elimity Insights will discard stored query evaluations that exceed this timeout during an import.
Support for pinning columns to stored queries
The owner or a stored query manager of a stored query can now pin its columns from the column selector, using the new 'pin columns' option. Pinning columns sets the default columns for the query: everyone who opens it will start with these columns selected. Pinned columns can include attributes, the entity identifier, and columns from linked entities.
Newly created stored queries start with all attributes pinned, and 'reset to default' restores this at any time. Pinning only sets the starting point, so anyone viewing the query can still change their own columns afterwards. You will only see and pin the columns you are permitted to view, and columns pinned by others that you cannot access are left unchanged.
Bug fixes & improvements
Prevent large peer review tables from crashing the browser
When a peer review contains more than 10,000 cells, Elimity Insights no longer renders the table automatically, since a table that large can seriously degrade your browser's performance. Instead, the page reports the number of cells and offers two options: click 'Download' instead to export the full peer review to Excel without rendering it, or click 'Render anyway' to display the table in the browser regardless.
Minor bug fixes & improvements
As always, this new release brings some smaller bug fixes and improvements:
Elimity Insights now writes a connector log when executing stored queries during an import.
The GitHub built-in connector now skips unresolvable team members instead of aborting the import.
Access review page now refreshes the data on clicking the 'finalize and send' button.
Elimity Insights now rejects stale snapshots when running multiple imports for the same source.
The DocuSign built-in connector no longer skips the first entry when retrieving users.
The LDIF built-in connector now checks if the file is UTF-8 encoded.
The failing source's name is now displayed in the subject of failure emails.
Deployment changes
New queryTimeOutMinutes configuration option
Elimity Insights now provides a new configuration option to timeout queries for which evaluation takes too long. More specifically you can now add a queryTimeOutMinutes option in config.hjson to set the maximum query evaluation time in minutes. By default Elimity Insights applies a timeout of 10 minutes, customers using complex queries on large data sets should consider increasing this value.
Migration information
To migrate from v3.45.x to v3.46.0, we suggest the following steps:
Make a backup of your existing database.
Make a backup of your existing installation directory.
Upgrade your installation by bumping the container image version.
Migrate your database, as described in our dedicated documentation.
Start the server and validate that it works as before.
Last updated