This release introduces a range of enhancements designed to improve planning, execution, visibility, and automation across the Cutover platform.

Highlights include several improvements to the AI Assistant, making it easier to navigate insights, understand recommendations, and take action directly from conversations. We've also expanded Multi-Runbook Dashboard capabilities with Stream support in the Runbook Completion Matrix, introduced the ability to create new runbooks from historical versions, and improved workspace usability by allowing filters to persist across Templates, Runbooks, and Snippets.

The Editable Nodemap continues to evolve with new filtering and task management capabilities, giving teams greater flexibility when working with complex plans. For developers and integration teams, we've added new capabilities to support incident management, automation, and operational governance, alongside the launch of the new Integrations Script Builder, which simplifies and accelerates the creation and deployment of custom integrations.

We've introduced several improvements to the AI Assistant to make it easier to navigate insights, understand recommendations, and take action directly from the conversation.

Suggested prompts are now organised into contextual categories that adapt based on your runbook's stage. In Planning mode, prompts are grouped into areas such as summaries, readiness, risks, timelines, ownership, and communications, while Execution mode also includes issue management and decision-support categories.

Analysis results have also been improved to display recognizable user and team names, making AI-generated insights easier to understand and act on.

In addition, the Assistant can now update the message body and recipients of existing Email and SMS tasks, helping you manage communications more efficiently without manually editing task configurations.

To learn more about our AI Assistant, click here.

The Runbook Completion Matrix now supports Streams as a cross-reference attribute on both axes. This means you can view application recovery progress broken down by stream — with substreams automatically rolling up into their parent — alongside existing options like Runbook Type, Folder, Team, and Custom Fields.

We've also added the ability to toggle between runbook count and task count, and to hide empty rows and columns for a cleaner view.

To learn more, see our multi-runbook dashboard article here.

You can now create a new runbook from any previous version — not just the current one. When viewing a historical version of a completed runbook, simply click "Create a runbook from this version" in the banner to duplicate it. This is especially useful when a plan has evolved significantly and you need to reuse an earlier configuration without rebuilding it from scratch.

To find out how to create a runbook, click here.

Filters you apply in your workspace (such as Project and other shared filters) now remain active when switching between the Templates, Runbooks, and Snippets tabs. You no longer need to reapply filters each time you navigate between views.

Where a filter applies to both tabs, it carries across automatically. Filters that are specific to a particular tab are cleared when switching to a tab where they don't apply, ensuring results remain relevant to the view you're using.

To find out more about navigating your workspace, click here.

We've introduced new editing capabilities to make managing tasks in the Editable Nodemap even easier. You can now select an area of the Nodemap (press and hold Shift while dragging) and apply filters directly to the selected tasks using the action menu that appears.

We've also improved task placement flexibility by allowing tasks to be moved or copied before or after tasks that do not have predecessors or successors. Simply drag a task onto the + indicator to move it, or hold Option (macOS) / Alt (Windows) while dragging to create a copy.

To find out more about the Editable nodemap, click here.

Our newest release includes several enhancements to support incident management, automation, and operational governance. New capabilities make it easier to integrate incident-related processes with runbooks, enforce participation requirements for critical tasks, and improve visibility into task status.

We've also expanded user and team information available to integrations and improved how the platform communicates when actions cannot be performed, helping create more reliable and predictable automation workflows.

Visit our Updates page on the Developer Portal to find out more.

We're excited to introduce the Integrations Script Builder - a new way to create and deploy Cutover Custom Integrations faster than ever.

Choose from pre-built templates across 10 categories - including ITSM, CI/CD, AWS, Azure, GCP, Observability, Communication, Security, and Documentation - or build a custom integration from scratch.

The builder simplifies setup by generating a deployment script that can automatically create the integration connection, custom fields, actions, and an optional companion runbook template in your Cutover instance.

Getting started is simple:

In just a few minutes, you can go from selecting a template to deploying a fully configured Custom Integration. To find out more, visit our Developer Portal pages here.

The listed issues and their replication steps are organized based on their potential impact on customers.

As well as bug fixes and platform improvements, our newest version introduces a major security enhancement with support for Post-Quantum TLS 1.2 cipher suites, helping strengthen secure communications across the platform. This release also includes Developer Portal updates with new API enhancements for automation and integrations. We’ll also soon be introducing the new Integrations Script Builder app to make building custom integrations faster and easier.

Our most recent Developer Portal release introduces new Incident Management endpoints, enhanced task progression controls, and refined API error handling to support more advanced operational workflows and automation use cases.

Highlights include dedicated Incident Management endpoints, new minimum user requirements for task start and completion, the addition of the is_late task attribute for workflow monitoring and alerting, and expanded user/team metadata support. We’ve also improved status-based API responses to provide clearer handling of restricted actions across archived, completed, and non-editable runbooks.

For full endpoint details, examples, and implementation guidance, please see the Developer Portal Updates page.

We’ll also soon be introducing the new Integrations Script Builder app, designed to help developers create, configure, and deploy custom integrations more quickly using pre-built templates and guided setup. Watch this space!

The listed issues and their replication steps are organized based on their potential impact on customers.

Our packed 2026.9 release focuses on improving runbook planning, execution control, and usability across the platform. Highlights include the introduction of the new Editable Nodemap for visually managing complex runbooks, enhanced task controls that allow specific users to be required for task start and completion, and improved task type editing that preserves manually configured durations.

This release also includes usability improvements to custom fields and RTO filtering, continued developer enhancements through the Developer Portal and upcoming Integrations Script Builder app, as well as advance notice of an upcoming TLS security enhancement planned for version 2026.10. Together, these updates provide greater visibility, flexibility, and control when managing large-scale operational workflows.

The new Editable Nodemap provides an interactive way to plan, manage, and execute runbooks, giving you a real-time view of tasks, streams, dependencies, and overall progress in one place.

Tasks are displayed as nodes, with relationships showing how tasks connect and execute throughout the runbook. You can zoom, pan, and navigate complex runbooks more easily while maintaining visibility into task sequencing, readiness, and execution flow, helping teams manage large-scale runbooks with greater clarity and control.

To find out more, see our Editable Nodemap articles here.

You can now define minimum number of users required to start or complete a task in the task’s advanced settings, giving you tighter control over sensitive execution steps and making it easier to enforce sign-off or participation for critical tasks. All changes are captured in the audit log and available via the API.

For further information, see our Task Advanced Settings article here.

Previously, changing a task’s type (for example, from “Normal” to “Validation”) would reset the task duration to the new task type’s default value, overwriting any manually configured duration. This affected both single task edits and bulk edits, particularly in larger runbooks where users needed to change task types without losing time-sensitive duration data.

Manually configured durations are now preserved when switching between non-auto-finish task types. When moving from an auto-finish type to a non-auto-finish type, the duration is reset to the new task type’s default value. Switching to an auto-finish type (such as a Milestone) will set the duration to zero, with a clear informational message explaining why.

Bulk edit now also includes new duration controls:

For more information, see our Task Types article here.

The custom fields modal during task creation and inline editing in the Task List now only appears if at least one required custom field is present. Previously, the modal would display whenever any custom fields existed, even if none were required. Users can still edit optional custom fields from the task edit panel after creation.

You can now filter templates by RTO Configuration Status on the workspace Templates tab, matching the filtering already available on the Runbook and Dashboard tabs.

For more information about RTO and about the filter options, please see our Help Center article here.

For all API-related updates such as new endpoints, examples, and integration changes, please see our Developer Portal. We’ll also soon be introducing the new Integrations Script Builder app, designed to help developers create, configure, and deploy custom integrations more quickly using pre-built templates and guided setup. Keep an eye on the Developer Portal for upcoming updates and documentation.

The listed issues and their replication steps are organized based on their potential impact on customers.

This release improves integration reliability and troubleshooting, with clearer OAuth error messages and more intuitive re-authentication prompts when connections expire.

OAuth error messages for integrations (e.g. Azure, AWS, Google, Okta) are now clearer and more specific. Errors now indicate when issues originate from the external identity provider, helping users and admins identify and resolve authentication problems faster.

If your integration connection has expired or been cleared, Refire Integration will now prompt you to re-authenticate (instead of showing a generic “Unknown” error), so you can reconnect and retry quickly.

We’ve added a new article to our Developer Portal website introducing system parameters—a secure, centralized way to manage shared configuration across integrations, automations, and runbooks. This allows you to store reusable values such as API keys, tokens, and URLs, reduce hardcoding, and simplify updates by managing everything in one place. To find out more, see the System Parameters page in the Developer Portal.

Note: For all other API related updates such as new endpoints, examples and integrations changes, please see our Developer Portal.

The listed issues and their replication steps are organized based on their potential impact on customers.

This release introduces improvements to the AI Assistant and audit logging to enhance usability and transparency.

You can now retry an assistant response in Workspace and Runbook if something goes wrong or you’d like it to try again. The previous response is cleared and replaced with a new one, making it clear which prompt is being retried.

For more information about AI Assistant, see our article here.

You can now see whether a snippet was added manually or via a task, providing clearer context on how snippets are created within a runbook.

To find out more about Snippets, see our article here.

Note: For all API related updates such as new endpoints, examples and integrations changes, please see our Developer Portal.

The listed issues and their solutions are organized based on their potential impact on customers.

This release brings several usability improvements to help you navigate, search, and manage tasks more efficiently.

Task IDs in Dashboard Starred Comments are now clickable, opening the Task Edit panel directly. Runbook task search supports multiple keywords, so you can find tasks faster in a single query.

Nodemap updates include new task indicators, improved navigation and highlighting, and smoother task interactions, making it easier to view statuses, dependencies, and work within complex runbooks.

These enhancements streamline workflows and improve visibility, helping you manage tasks more quickly and effectively.

Task IDs in the Dashboard's Starred Comments section are now clickable, allowing you to open the Task Edit panel directly for faster access without additional navigation.

The runbook task search bar now supports multiple keywords - enter comma-separated terms (e.g. test, run) to return tasks matching any of them. Spacing around commas is handled automatically and will return the same results. This new functionality works seamlessly alongside existing filters and streams.

We’ve introduced a set of small updates to the Nodemap to improve clarity, navigation, and overall usability. These changes also lay the groundwork for the upcoming Editable Nodemap experience. We’ll tell you more about this very soon!

New visual indicators have been added to improve visibility at a glance, including:

When filters hide predecessor or successor tasks, nodes now display an indicator—hover to view task details and click to reveal the hidden dependencies.

Predecessor indicator:

Successor indicator:

When an indicator is clicked:

Improved task interaction

Better navigation and visibility

Other Nodemap updates

These updates make the Nodemap easier to navigate and understand, while preparing for more advanced capabilities in future releases.

The listed issues and their solutions are organized based on their potential impact on customers.

This release delivers several behind-the-scenes improvements and incorporates feedback from our customers. While there are no new major features in this update, these refinements ensure Cutover's continued smooth performance and set the stage for future enhancements.

The listed issues and their solutions are organized based on their potential impact on customers.

To reduce visual clutter and add clarity, the RTO Workspace filters will only become available when the RTO setting option has been enabled first for at least one Runbook type within the Workspace.

Find out how to enable and implement RTO/RTA, visit the Help centre article.

When the user creates a new runbook version, a loading spinner will now appear, clearly indicating that the system is processing your request.

To prevent mid-action editing conflict, while the version is being created, all screen interactions for the user creating the new version are temporarily disabled.

We’ve made a couple of updates and improvements to Cutover Connect, bringing more secure credential handling and documentation capabilities:

For all Cutover Connect related information, please see our Developer Portal.

This release introduces improved runbook controls, better task visibility, and enhanced filtering to help you manage workflows more effectively.

Runbook Controls

New settings allow you to:

Task Visibility

Integration Improvements

Filtering Enhancements

For all API related updates such as new endpoints, examples and integrations changes, please see our Developer Portal.

The listed issues and their solutions are organized based on their potential impact on customers.

Selected tasks now clearly show when they are used as the RTO Start for child tasks. Associated child task IDs are displayed in the parent view, making RTO relationships and dependencies easier to understand at a glance. If a task serves as the RTO Start for multiple children, all relevant task IDs are shown.

To learn more about RTO/RTA, see our article here.

For all API related updates such as new endpoints, examples and integrations changes, please see our Developer Portal.

The listed issues and their solutions are organized based on their potential impact on customers.