---
title: Turbine On-Prem 26.5.3 Release
slug: turbine-release-notes/turbine-on-prem-2653-release
createdAt: 2026-11-06T04:18:30.871Z
---

Turbine On-Prem **26.5.3** delivers a hotfix that restores editing of playbook conditions.

## Addressed Issues

### Playbooks

- **Changes to Existing If Action Conditions Were Not Saved** — Fixed an issue where editing the conditions of an existing **If** action in a playbook or component and clicking **Apply** discarded the change and left the **Save** button disabled. Reopening the action showed the original conditions. Condition changes now stay after you click **Apply**, and you can save the playbook or component.
- **Playbook Record Actions Failed When Workflows Required Fields Were Not Populated by the Playbook:** Previously, fields which were originally optional based on Application Builder configuration, but then marked as **Required** by a Workflow were validated on the front end only. Starting with 26.5, validation was extended to the backend to ensure required fields were enforced on the API side as well. That broke a specific scenario where playbook record actions could fail if it changed a value based of which a workflow made some other fileds required and they are not populated with any value. 
  This release allows playbook record actions to bypass the required-field validation when the field is not originally required but made required by a workflow. This enables records to be saved even when workflow-mandated fields are left empty for analysts to complete later. Fields marked as **Required** in Application Builder continue to be enforced unless a workflow explicitly makes them optional.
  This change applies only to playbook record actions. Saves through record forms and APIs are not affected.