Release Notes 3.7 (July 2025)

User Budgets and Alerts

Admins can now define monthly compute budgets for users and receive automated email notifications as they approach or exceed their monthly allocation. This helps monitor usage and prevent unexpected costs without disrupting workflows.

Key highlights:

• Automated Alerts: Email notifications are sent to designated recipients when a user reaches 75%, 90%, and 100% of their monthly compute budget.

• User Visibility (Optional): Allow users to view their allocated monthly budget and current usage directly from their Account page.

• Default Budget: Set a default monthly compute budget (USD) for all users.

• Custom Budgets: Assign user-specific monthly budgets, which override the default setting.

This feature gives users and administrators greater insight and control over compute consumption while maintaining uninterrupted access to resources.

To enable this feature and set budget alerts for users, configure email notifications using your SMTP server via Integrations as explained in our Admin Guide here.

Pipelines - Queue Time & Compute Environment Utilization

Users can now view Queue Time from the Pipelines IDE, which can help users estimate when their Pipeline will start. For a deeper view of Compute Environment utilization and capacity, users can click View Advanced Details in the Queue Time pop-up.

This feature gives users greater transparency into system load and helps inform decisions around run timing, especially during periods of high compute demand.

Queue Time

Cloud Workstation - Improved Idleness Detection

To optimize resource usage, Cloud Workstation sessions with CPU activity below 5% for 2 hours now trigger a UI prompt asking if the user wants to keep the session active. If there's no response after 5 minutes, the Compute Workspace will be automatically placed on hold to conserve resources.

Admin - Release Management

Admins can now manage who can view runs associated with Release Capsules and Pipelines.

• Restricted Run Visibility: By default, runs are only visible to the user who initiated them, helping to protect user and data privacy.

• Optional Shared Visibility: For enhanced transparency or collaboration, enable shared run visibility to make runs visible to all users with access to the release Capsule or Pipeline.

Admin - Wildcard Support in Assumable IAM Role CFN Parameter

Admins can now specify role ARNs with wildcards in the Assumable IAM Roles CloudFormation parameter.

This enables granting access to multiple roles that share a common ARN prefix or path without updating the CloudFormation stack, reducing the need for stack modifications and avoiding downtime.