Maestro release notes

Data Fabric queries now support the qem: (Query Expansion Multiple) prefix in addition to the existing qes: (Query Expansion Single) prefix. Queries using qem: return all matching records as an array of up to 1,000 items, enabling workflows to fan out over multiple Data Fabric records in a single step. Queries using qes: continue to return a single record.

Additionally, qes: now returns an explicit error when the query matches more than one record, and returns an empty result when no match is found, instead of failing the workflow.

For more information, see Data Fabric operations in Maestro.

Maestro now shows a warning indicator when a workflow instance is being throttled due to high activity volume:

The indicator updates in near real-time and disappears automatically once throttling lifts. Throttling affects execution speed only — your workflow continues to run and produces the same results.

For more information, see Instance throttling.

Quick Form HITL tasks now register their schema with Orchestrator before task creation using ITaskSchemasClient.CreateSchemaAsync. Schema registration is idempotent — if the schema already exists (HTTP 409), it is treated as success and task creation proceeds normally. TaskCreateRequest now uses the native TaskSchemaKey (GUID) and Type = QuickFormTask properties from the v26 client, replacing the previous AdditionalProperties stub. A new error code HitlTaskSchemaRegistrationFailed (170042) is returned if schema registration fails.