Maestro release notes

This is for:

Developer System Administrator

This page summarizes the changes delivered with every update of Maestro, the software that manages and monitors your local workers and the State Store.

Maestro updates are automatic to allow you to benefit from the latest features and bug fixes. They also prevent the Crawling Module from becoming incompatible with the Coveo Platform.

If Maestro is two or more versions behind after a disconnection from the Internet or a server shutdown, the workers will stop until Maestro is up to date again. See Updates for details.

April 21, 2025 update: Maestro 2.0

Automatic updates

Important
Important

This release changes the way checksums are set on Maestro packages. Automatic updates from versions prior to 1.96 no longer work from this version onward.

If installing Maestro on a new host, it is crucial that you start from a version of Maestro’s installer from September 2024 or after. To ensure you have the latest version, download the installer from either the Installing Maestro article or the Crawling Modules (platform-ca | platform-eu | platform-au) page of the Coveo Administration Console.

Embedded browser

The embedded browser packaged with Maestro now uses Microsoft Edge WebView2, replacing Chromium and Chrome for Testing. We expect this change to greatly improve maintainability of the embedded browser.

Maestro’s installer automatically checks for the presence of the WebView2 runtime and will install it if it’s not present on the host. As such, no manual action is required from users.

REST API source

Additional startup validation is now performed to bring visibility to invalid configurations:

  • The source now detects if a PayloadJsonContent is set and the endpoint’s method is not set explicitly to POST. This misconfiguration was mostly found in SubItems and RefreshEndpoints arrays.

  • The source also detects if a dynamic value is found in the request element of a top-level Endpoint or RefreshEndpoints array, under Path, QueryParameters, PayloadParameters, or PayloadJsonContent. Dynamic values require a previous request to extract data and therefore are not valid when performing an initial query. This validation can also fail if a RefreshEndpoints array is a child of a SubItems array, as these calls would never be performed. The fix is to remove or replace the dynamic values.

Web and Sitemap sources

The Chrome driver used for JavaScript rendering has been updated to Chrome for Testing v134.

April 07, 2025 update: Maestro 1.107

REST API sources

It’s now possible to skip request timeout errors caused by unresponsive API calls (taking over 5 minutes by default), instead of stopping the source update operation.

To do so, in your source configuration, add error code 408 under SkippableErrorCodes.

Confluence sources

Added support for indexing a root space from the starting addresses in the new URL format [URL]/spaces/[KEY] that is introduced in Confluence Data Center 9.

Existing formats remain supported:

  • [URL]/spaces/viewspaces.actions?key=[KEY]

  • [URL]/display/[KEY]

Handling of space type filtering parameters has been improved as well.

Web and Sitemap sources

The Chrome driver used for JavaScript rendering has been changed from Chromium to Chrome for Testing (v133).

Chrome process management has been improved as well.

Note

On a fresh installation of Maestro, using the embedded browser locally on the Maestro host will display a banner mentioning it is intended for testing purposes.

The next release of Maestro will include a new embedded browser without this banner.

GraphQL API sources

Improved support for error codes returned by GraphQL APIs.

Jira and Confluence security identity providers

Added checkpoint progress reporting in the security identity providers to avoid timeouts when expanding large identities.

March 10, 2025 update: Maestro 1.106

System

This release includes fixes for all connectors:

  • Fixed an issue introduced during the migration to .NET 8, where new exception types from temporary communication failures were not retried. This stopped source execution with an UNABLE_TO_INDEX_DOCUMENT error.

  • Fixed an issue where Maestro didn’t automatically relaunch killed worker processes, potentially reducing operational capacity until a host restart.

February 19, 2025 update: Maestro 1.105

System

  • This release removes the original implementation of the WorkerService, and with it the UseNodeAgentCore parameter setting in Maestro’s settings file.

  • The .NET Framework is no longer installed by Maestro’s installer. Installing it on Maestro hosts is not a requirement to run Maestro from this version onward.

  • Crawling and Security Workers are now built using .NET 8, unlocking new language features and optimizations!

REST API and GraphQL API sources

Extended metadata actions are now available for REST API and GraphQL sources.

Web source

Improved handling of HTTP request errors in the Web source.

January 22, 2025 update: Maestro 1.104

System

  • Maestro and its new Worker Service are now built using .NET 9, unlocking new language features and optimizations!

  • As the software is self-contained, there’s no need to install the .NET 9 runtime on Maestro hosts.

REST API source

  • Pagination tokens like @offset and @pageSize can now be used in the PayloadJsonContent property of a REST API source configuration. Setting UsePayloadTokens to true in the Parameters section of the Paging configuration ensures that the Offset and Limit parameters, which are normally required, are no longer included in the query URL or required. More details are available in the OffsetType documentation, under Cursor-based pagination with POST requests.

  • XML-formatted API responses are now supported.

Web and Sitemap sources

The Chrome driver used by these sources has been updated to major version 131.

Sitemap source

Fixed an issue where the HTML Sitemap parser would fail on URLs containing encoding characters.

File source

  • Improved the error message for faulty starting addresses.

  • Fixed an issue where ForceInitialRebuild would prevent deleting documents.