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.

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.