[Community] - [Agentic Orchestration] - Reports of failures in expression evaluations related to the HITL task output parameters

Update timeline

1. investigating Aug 18, 2026, 05:54 PM UTC

   We are investigating reports of an outage impacting failures in expression evaluations related to the HITL task output parameters for Asgentic Orchestratron in community users in Europe. Impact: Users may be unable to complete HITL tasks Next update: Our teams are working to understand the cause and scope and will share updates as available.

2. identified Aug 18, 2026, 07:17 PM UTC

   We have identified the cause for an outage impacting expression evaluations related to the HITL task output parameters for Agentic Orchestration in community users in Europe. Impact: Users will experience failures when they have an expressions using HITL task output parameter. Next update: Our teams are working to understand the cause and scope and will share updates as available.

3. identified Aug 18, 2026, 08:31 PM UTC

   We have identified the cause for an outage impacting expression evaluations related to the HITL task output parameters for Agentic Orchestration in community users in Europe. Impact: Users will experience failures when they have an expressions using HITL task output parameter. Next update: Our teams are working to understand the cause and scope and will share updates as available.

4. identified Aug 18, 2026, 09:45 PM UTC

   We have identified the fix and the resolution is in progress. Next update: Our teams are working on the fix and will share updates as available.

5. monitoring Aug 18, 2026, 10:53 PM UTC

   We have deployed the fix and are monitoring the resolution. Next update: Our teams are monitoring the resolution and will share updates as available.

6. resolved Aug 18, 2026, 11:25 PM UTC

   The outage has been resolved and Agentic Orchestration is fully operational. Impact: No ongoing user impact.

7. postmortem Oct 08, 2026, 01:15 AM UTC

   ## Customer impact Between August 18, 2026 at 3:24 pm UTC and 11:25 pm UTC, Agentic Orchestration processes in the subset of users from the Europe region that read fields from a completed human-in-the-loop task could have failed at the expression step. No customer impact was reported: the change reached only the Community ring and the affected feature is rarely used. Paid rings were not affected. No data was lost or changed. ## Root cause The Maestro backend was upgraded to a newer version of the Orchestrator client library to fix an unrelated issue. The new version renamed the fields in the human-in-the-loop task output, and Maestro passed those names straight through to customer expressions, so expressions written against the old names stopped working. This backend change was only in the Community ring. At the same time the process designer was updated to show the new field names in all rings, so outside Community the designer offered names the backend did not return until that change was reverted. ## Detection The issue was detected at 3:24 pm UTC on August 18, 2026 by the team in the Community ring. The incident was declared at 5:28 pm UTC and a public status update was posted at 5:54 pm UTC. ## Response At 5:53 pm UTC the team decided to revert both changes. The designer change was reverted in all rings at 8:24 pm UTC. The backend library upgrade was reverted in the Community ring at 10:49 pm UTC and the incident was marked mitigated at 10:53 pm UTC. At 11:25 pm UTC the fix was verified and the incident was marked resolved. ## Follow up 1. Define the task output contract in Maestro so upstream library changes cannot alter it 2. Add specific automated tests for the task output contract 3. Coordinate designer and backend schema changes in the same release