Orchestrator release notes

When deploying a solution, a Default Serverless template is now automatically attached to ensure automations can run without additional setup.

This removes the need to manually configure machine templates and helps avoid common deployment issues where processes fail due to missing runtimes.

Scheduled agentic jobs now correctly display their source as Trigger instead of Manual in Job Events and Maestro.

This ensures better visibility into how processes are started, helping users distinguish between manually triggered and scheduled executions.

Restarting a failed job now correctly retains its input arguments, even when they were stored as an InputFile.

Previously, jobs with large inputs could lose their configuration on restart, requiring users to manually re-enter arguments. This update ensures a smoother restart experience by automatically restoring the original inputs.

A new IXP Models permission is now available at the folder level, giving you more control over access to IXP models.

You can also assign this permission in custom folder-level roles to fit your access control needs.

You can now control whether asset values can be accessed outside of automations using the new Access Scope setting.

When creating or editing an asset, choose one of the following options:

This gives you more flexibility while maintaining control over sensitive data.

Existing assets are not affected. By default, they remain set to Automations only unless explicitly changed.

You can now retrieve a specific asset by its name using the GetAssetByName endpoint.

This is useful when you already know the asset name and want to fetch its value outside of an automation workflow.

For more information, check the Retrieving a specific asset by name section from the Assets requests page in the Orchestrator API guide.

We updated the default Orchestrator landing experience so that navigating to the main Orchestrator route now opens the Tenant Overview page instead of the folder-level homepage.

If needed, you can manually save the folder-level homepage URL as a browser bookmark for direct access.

For more information about the improved Tenant Overview experience, including additional enhancements such as cross-folder jobs visibility, check the Tenant section from the Orchestrator user guide.

The Job details side panel now displays a warning when a job is started using input arguments sent as attachments due to input size restrictions. The message provides guidance on resolving compatibility issues with robot versions.

For more information, check the About input and output arguments.

The Job Details side panel now includes a new Compatibility field within the Execution Environment section.

This addition provides clearer insight into the environment compatibility of each job, helping you better understand how and where jobs are executed.