Mayo de 2026

May 25, 2026

hitlTask output variable for Human-in-the-Loop tasks

When a Human-in-the-Loop (HITL) task completes, Maestro now exposes the full task response as a hitlTask output variable alongside the existing Action output. Previously, workflows could only read the action the completing user took. Downstream steps can now read all task details from the App Tasks API response, including assignee information and the task key.

For more information, see User task.

IXP Extraction activity: jobAttachment digitization mode

The IXP Extraction activity now accepts a jobAttachment digitization mode in addition to the existing fileUpload mode. In jobAttachment mode, the attachment identifier, file name, and MIME type are supplied as individual inputs. Workflows that receive job attachments directly from Orchestrator can now invoke document extraction without first resolving a downloadedFileOutput reference. Workflows that supply an unrecognized mode receive the error code IdpDigitizationModeNotSupported instead of a generic input validation error.

Reduced write overhead for high-throughput workflows

Maestro now excludes unbounded and large-data paths — such as run history arrays and AI recommendation arrays — from Cosmos DB indexing on the Instance, ElementExecution, and Incident containers. This lowers write request unit (RU) consumption for high-throughput workflows, especially multi-instance subprocesses and case management scenarios. Maestro reconciles existing containers to the new indexing policy on startup — no action required.

Corrección de errores

• Fixed a runtime exception that occurred when recording activity errors if a log field's string representation was null. Error-logging paths now handle null values gracefully.