In this release we have the following updates:

You can now update custom field data in dynamic runbooks whilst a task is in progress, providing greater flexibility and control during execution. To find out more about editing tasks within a runbook, see our Add tasks to a runbook article.

Users with the Custom Field Admin role can now edit and archive custom fields. This improvement provides greater flexibility in managing setup and configuration, enabling admins to maintain and adjust custom fields as needed without relying on additional support. For more information, please see our Create Custom Fields article.

Cutover AI enhancements (optional add-on):

Cutover users can now enhance their experience with the optional Cutover AI add-on. This feature provides AI-powered capabilities to summarize, suggest improvements, and even automatically create runbooks. Cutover AI is available for an additional fee.

We’ve introduced improvements to the Cutover AI add-on. Recent updates include:

Interested in using Cutover AI? Please contact your Customer Success Manager (CSM) for more details.

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

In this release we have the following updates:

The Task Stage Summary, Task Completion, Task Split, and Runbook List components on the Multi-Runbook dashboard are now clickable. You can click within each component to view task details and navigate directly to associated runbooks.

Additionally:

See our Multi-Runbook Dashboard overview article for more information.

You can now measure Recovery-Time Actuals (RTA) and compare them against Recovery-Time Objectives (RTO) within your Cutover runbooks. These metrics provide insight into whether a service meets its target policy. RTO/RTA calculations update automatically as tasks start or finish and are displayed at the runbook level. See our Measure RTA and compare against RTO article for more information.

We’ve been making improvements to create a smoother and more seamless experience in Cutover. These enhancements will be introduced gradually through a phased rollout over the next few releases. Please speak to your Customer Success Manager (CSM) if you have any questions.

Here is a list of some of the key visual changes that you’ll notice:

Audit log now easier to navigate

We’ve made it easier to filter and search the audit log. All actions are now displayed in a single list, reducing the need to click through pages of results. This option can now be found in the top menu bar rather than having to click through Settings. Plus, you can now filter by task ID, user, action type, and date/time to find what you need faster. See our Runbook Views article for more information.

Enhanced text editor - more formatting options

Our text editor just got an upgrade. You now have more formatting options, including headings, bullets, numbering, and alert boxes for highlighting important content. To enhance security, adding new images via drag-and-drop is no longer supported. See our Text Editor article for more information.

Task Skipping Now Available for Runbook Team Members

Runbook team members can now skip their assigned tasks. However, tasks with advanced conditions (like “Everyone must start” will still require an admin to skip). See our Execute a runbook article for more information about skipping tasks.

Task start and task finish modal improvements

Task action buttons (e.g., Start Task, Complete Task) are now disabled if you don’t have permission, or if the task can’t be started/completed or is in the process of being updated by another user.

Additionally, task IDs are now displayed in the title of the task start and finish modals, making it easier for task executors to identify their tasks. To find out more about executing a runbook, read our help center article here.

Restore previous runbook warning

We’ve added a new warning when restoring a previous runbook version to help prevent accidental changes. To find out about runbook versions, see our help article here.

Post Implementation Review - no more publishing

No need to publish anymore! Now, all users with access to the runbook can view the dashboard automatically. For more information on the PIR dashboard, see our help article here.

Linked tasks naming

No more manual naming! Linked tasks now automatically inherit the template’s name but can still be renamed in the edit panel if needed. To find out more about creating linked tasks, see our help article here.

Improved bulk task management

Managing bulk actions, such as updating or deleting tasks, just got easier. Tasks you can’t update (due to permissions or status) will be skipped, while all others update or delete successfully. Before saving any bulk actions, a confirmation message will appear. To find out more about bulk editing tasks, see our help article here.

Streamlined Settings menu

We’ve reorganised the Settings (cog) menu so that items are now grouped logically by action type, and less frequently used options have been removed for a more streamlined experience. Some options, like ‘Merge a runbook’, have been renamed to improve terminology consistency.

New Team filtering options

We’ve added two new filters to the Team section: 'No Value Set' to view tasks not assigned to any team and 'Any Value Set' to see all tasks assigned to a team. For more information on filtering, please see our help article here.

API Updates

There are no notable fixes to be shared in this release.

This release contains bug fixes and minor internal improvements.

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

This release contains bug fixes and minor internal improvements.

You can now manage custom field groups using the Cutover API. See the Endpoints page to find out more.

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

In this release we have the following updates:

Data Sources workspace view: You can now see a centralised and interactive view of your entire application portfolio, clearly indicating which applications have plans, their coverage levels, and associated metadata. Use this view to identify gaps, ensure readiness, and streamline planning.

Easy homepage access

Click the Cutover logo in the top-left of the platform now takes you to your Cutover homepage.

Ability to view archived runbooks: You can now view archived runbooks without needing to restore them first. The archived runbooks are in a read-only state and if you need to make changes, you must restore the runbook. Please see our Archive runbooks article for further information.

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

In this release we have the following updates:

Add failing conditions into the Polling tab

You can now set failure values in the Custom Integration Polling tab to define when a polling integration should fail. This ensures that Polling integrations will stop when a specified condition is met. For more details on this update, please see the Polling tab in our Developer Portal.

Stream completion component on Multi Runbook Dashboards (MRDs) is now clickable

You can now interact with the Stream Completion component to see the live status of your streams and different runbooks and take action when needed. Hover over any colored stage to see the number of runbooks, and click on a stage to view and access the related runbooks.

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

In this release we have the following updates:

Changes for teams when importing a CSV file

We’ve made it easier to create new teams or add existing teams when you import a CSV file.

For more details refer to:

Export and Import tasks for information on importing tasks via CSV.

Create Runbook Teams for details on Linked Teams.

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

In this release we have the following updates:

Ability to lock folder destinations for runbooks and templates

You can now lock runbooks to a folder on creation from a template. This is helpful if you prefer to have all your runbooks created and run in the same location, making it easier for everyone to access the correct runbooks. When creating from a template this helps to ensure the correct destination folder options are available in the duplicate or merge modal.

Key Details:

Folder lock on creation: When creating a runbook from a template with a folder lock, the folder field is read only and cannot be changed.

Duplicating runbooks: The folder lock does not apply when duplicating runbooks, even if they were created from a locked template. You can duplicate runbooks into any folder but cannot move a runbook that was originally created from a locked template.

Merging runbooks: When merging a template to a new runbook, the new runbook will be locked to a folder (same logic as duplicating).

When merging into an existing runbook, the lock does not apply - users can still merge into any runbook, regardless of folder location.

Please see our Create a template or Manage Runbook Details article for further information.

Download Audit Log update

The audit log section will be removed from runbooks and replaced with a Download as CSV menu option within Runbook settings. You will still be able to download a CSV with the same format by clicking on the cog menu and choosing Download Audit Log. Please contact your Customer Success Manager (CSM) if you have any questions regarding this.

Text Editor changes

We’ve made some changes to our Text Editor. Please see our Text Editor overview article here to find out more.

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

In this release we have the following updates:

Ability to edit a task title and description when the task is in progress

You can now make changes to a task title or description whilst the task is in progress. This option applies to all runbook types: for dynamic runbooks, these can be edited in run; for non-dynamic runbooks, you will need to pause the runbook. To find out more about adding tasks to a runbook, see our help article here.

Maximum retries option added for polling

You can now set a maximum retries amount for integrations that require polling. The default value for new and existing integrations are 120 retries and this can be increased or decreased as required. You should review any Custom integration polling to ensure this number suits your needs.

Default polling interval value

The default polling interval value has been updated to 30 seconds for all new integrations.

Please see our Developer Portal for more information about these changes.

New Refresh data source option

You can now pull new fields and attributes from the data source by using the Refresh option which can be found in the three dots menu. Here you can also archive a data source too.

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