Turbine Cloud 26.5.1 Release
October 23, 2026
Turbine Cloud 26.5.1 resolves an issue identified during early 26.5 deployments that could affect record updates and playbook record actions. The issue was quickly identified and patched, minimizing customer impact. All record operations now work as expected.
Addressed Issues
Records
- Playbook Record Updates Failed or Ran Very Slowly β Fixed an issue that could cause playbook Update/Create Record actions to fail or run slowly when records were linked to thousands of other records. Record updates now complete more efficiently, without slowing down other record actions.
- Record Updates Became Unreliable After Heavy Load β Fixed an issue where a high volume of record updates could affect the subsequent updates and playbook runs. Record processing now remains efficient under heavy load.
- Records Fail to Save When a Workflow Requires a Field That Is Not on the Form β Starting in Turbine 26.5.0, saving a record also enforces workflow rules that make fields required, optional, or hidden. Before, only fields set as Required in Application Builder were checked. If a workflow action marks a field Required but that field isn't in the application's layout (for example, a field moved to the hidden fields section), the save fails with Field <name> must have value. The error appears whenever the workflow condition matches. Users can't fill in the field because it isn't on the form. The same validation applies to the playbook Create Record and Update Record actions. Those actions now fail when they leave a workflow-required field empty, even if the same save succeeded before 26.5. If the enforcement of required fields in workflow actions affects existing playbooks, in the application's workflow, find the action that marks the field Required and remove the field from it. If the field should stay mandatory, add it back to the layout. You can also point the workflow action at the field users actually fill in. For playbook record actions, map a value to every field the workflow requires for the record's conditions.
Known Issues
Playbooks
- Changes to Existing If Action Conditions Are Not Saved β In a playbook or component, when you edit the conditions of an existing If action and click Apply, the change is discarded and the Save button stays disabled. Reopening the If action shows the original conditions. This issue was introduced in Turbine 26.5.0 and affects all users. A fix is planned for an upcoming release.