Orchestrator release notes
June 2025
The audit log now specifies the reason for automatically disabling a trigger in the following scenarios:
-
The trigger was disabled upon exceeding the values defined in the tenant-level settings for Triggers - Disable when job creation fail count and Triggers - Grace period when job creation keeps failing count (days).
-
The trigger was disabled due to the trigger-level Set execution-based trigger disabled toggle being enabled and the values for Disable when consecutive job execution fail count and
Grace period on disabling the trigger (days) being exceeded.
Orchestrator now allows you to create disconnected event triggers, which you define from scratch, outside of an existing process. The new functionality, previously available in Integration Service, complements the existing Orchestrator capability to edit connected triggers defined as package requirements for a process. Therefore, Orchestrator now provides a unified trigger experience, enabling you to create and manage all types of triggers.
For details on creating disconnected event triggers, refer to Creating an event trigger.
Attempting to submit a single-step form with errors now highlights the first field where an error is detected.
The Folder Administrator role was missing the View, Edit, and Delete permissions for Test Case Execution Artifacts. We have fixed the issue.
