2026 年 5 月

May 11, 2026

Automatic serverless runtime for solution deployments

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.

新增功能

• A Default Serverless template is automatically added (if none exists)
• The template is inherited within the folder structure
• You can choose to disable this behavior via advanced deployment options

Correct job source for scheduled agentic processes

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.

Improved Resources search filter

You can now filter resources by entity sub-type directly from the Resources tab in the cross-folder Registry page, leading to more precise and relevant search results.

Input arguments preserverd when restarting jobs

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.

New folder-level permission for IXP Models

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

包含的内容

• Personal Workspace Administrator: View, Create, Edit, Delete
• Folder Administrator: View, Create, Edit, Delete
• Automation Developer: View, Create, Edit, Delete
• Automation User: View only

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

Direct API access for assets

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:

• Automations only (default): asset values can be used only within automation workflows.
• Automations and API: asset values can also be accessed programmatically via APIs and integrations.

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.

Retrieve a specific asset by name

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.

Sort resources by Type in Registry

You can now sort resources by Type in the Resources tab of the cross-folder Registry page, making it easier to organize and find specific entries.

Tenant Overview as the Orchestrator homepage

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.