Turbine Cloud 26.2.2 Release

july 21, 2026 turbine cloud 26 2 2 is a minor release that includes bug fixes and improvements addressing issues identified in the 26 2 0 release for details on the new features and enhancements introduced in turbine cloud 26 2 0, see turbine cloud 26 2 0 release notes https //docs swimlane com/turbine release notes/turbine cloud 2620 release addressed issues applications and records reference fields missing from reports and api responses resolved an issue where reference field values appeared in full record views but were empty in reports and record api responses reference field values now display correctly and consistently across all three duplicate comments created by repeated submissions fixed an issue where repeatedly clicking submit while editing a record comment created duplicate comments comment updates now process only one submission while the update is in progress playbook runs run again option missing for playbook runs fixed an issue where the run again button was unavailable for completed production runs in the test console the run again option is now available for completed production, test, and draft runs component outputs included unrelated upstream data fixed an issue where a component's published output included merged output from earlier connectors and sub playbooks published component results now contain only the output produced by the component action canvas discovered webhook outputs disappeared after saving fixed an issue where outputs discovered from webhook triggers disappeared after you saved, refreshed, or reopened the playbook discovered outputs now persist after saving or reopening the playbook record correlation triggers could be removed during cleanup fixed an issue where record correlation triggers were removed in certain edge cases when the orchestration task identifier differed from the correlation configuration identifier correlation triggers now remain available after cleanup processing transform actions could fail when using specific hashing configurations fixed an issue where the hash string transformation failed when generating md5 hashes for non security use cases workflows that use md5 for non security purposes now complete successfully in those environments note this fix does not apply to government cloud environments date and time transformation settings were missing or invalid fixed an issue where existing date and time transformation settings appeared blank, displayed invalid duplicate parameters, or were missing from the visual playbook editor these settings now display correctly and can be edited without creating invalid parameters enhanced charts experience dashboard chart layout issues new enhanced charts were introduced in 26 2 there were minor layout issues, so the enhanced charts experience has been disabled while the layout issues are addressed enhanced charts will be enabled by default in an upcoming release known issues get date/time inputs can be cleared when editing another transformation block in a transformation action with multiple blocks, editing and applying another block while a configured get date/time from playbooks block remains collapsed can clear the function's required input later playbook runs fail and identify the missing input workaround expand the get date/time from playbooks block at least once in the same editing session before applying the transformation changes you can collapse it again after expanding it recovery reopen the transformation action, expand the affected block, restore the missing input, and apply the changes