Bug fixes

View bug fixes in automation orchestrator for each release.

Version Bug fixes
2026.8 The initial release of automation orchestrator. There are no bug fixes associated with this release.
2026.8.1788958058

Workflow execution

Approvals

User management

Workflow execution (2026.8.1788958058)

  • Fixed an issue where agentic workflow steps did not enforce their configured timeout. An agentic step could run past the configured timeout limit without being cancelled. Agentic steps that exceed the timeout are now marked as timed out and cancelled. (AAP-87666)
  • Fixed an issue where unpublishing a workflow from the workflow builder displayed a “Failed to unpublish workflow” error with a gateway timeout message. The workflow was unpublished despite the error, but the misleading failure message is confusing. The unpublish operation now completes without delay. (AAP-87692)
  • Fixed an issue where task-agent response metadata returned duplicated scalar values. For example, the finish reason could appear as "stopstop" instead of "stop". (AAP-87759)

Approvals (2026.8.1788958058)

  • Fixed an issue where an approval step inside a loop failed on the second iteration with an HTTP 409 Conflict error. Approval nodes inside loops now generate unique identifiers per iteration. (AAP-87702)
  • Fixed an issue where saving a workflow with an approval node set to follow the system default for on-failure behavior displayed a false validation warning. The warning incorrectly stated that the fallback decision would have no effect unless "continue on failure" is enabled in the step settings, disregarding the admin system default. Workflow validation now correctly considers both step-level and system-level settings.(AAP-88713)

User management (2026.8.1788958058)

  • Fixed an issue where creating a user in Access Management failed if the First Name field was left blank. The form accepted the submission, but an error message appeared: “Failed to create user.” Users can now create accounts without providing a first name. The API now accepts these values and creates the user successfully. (AAP-86107)