Turbine Cloud 26.2.2 Release

july 21, 2026 turbine cloud 26 2 2 includes bug fixes that improve the reliability of record data, playbook configuration, and orchestration workflows for features and other changes introduced in the 26 2 0 release, see turbine cloud 26 2 0 release docid\ eyvfgddembqu33rahkydi addressed issues applications and records reference fields were missing from reports and api responses fixed 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 consistently across record views, reports, and api responses repeated comment submissions created duplicate comments fixed an issue where clicking submit repeatedly while editing a record comment created duplicate comments comment updates now process one submission while the update is in progress reports and dashboards dashboard chart layouts displayed incorrectly fixed an issue where enhanced chart rendering caused layout problems on some dashboards dashboards now use the established chart rendering experience playbook runs run again was missing for production runs fixed an issue where the run again button was unavailable for completed production runs in the test console run again is now available for completed production runs as well as 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 orchestration and 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 by cleanup processing 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 md5 hash transformations failed in supported commercial cloud environments fixed an issue where the hash string transformation failed when generating md5 hashes for non security use cases in supported commercial turbine cloud environments workflows that use md5 for non security purposes now complete successfully in those environments this fix does not apply to government cloud environments date and time transformation settings displayed incorrectly fixed an issue where existing adjust date/time and convert date/time settings appeared blank, adjust date/time displayed invalid duplicate parameters, or unix time conversion settings were missing from the visual playbook editor these transformation settings now display correctly and can be edited without creating malformed parameters