Turbine Cloud Release Notes
Turbine Cloud 25.2.0 Release
Addressed Issues
3 min
reports resolved an issue where special characters like \t and \n were incorrectly rendered as actual tabs or line breaks in reports these characters are now displayed properly, ensuring data appears as expected resolved an issue where charts failed to display values when record data included korean text chart labels and legends now fully support korean, japanese, arabic, and other character based languages, ensuring accurate and clear representation across multilingual record data canvas resolved an issue where some playbooks displayed incorrect names and opened the wrong page when accessed from the orchestration → events view with this update, playbook names now appear correctly and open in the expected canvas editor resolved an issue where playbooks could not be saved if an action included discovered outputs with nested array data the issue caused an error during save, especially when outputs had advanced structures playbooks with advanced output structures now save correctly without errors resolved an issue where conditions set in actions inside parallel groups within loops were not visible in the ui now, these conditions correctly show up, making it easier to view and update them when configuring playbooks resolved an issue causing a “system error” when accessing job details for component runs older than one hour details are now displayed without any issue records resolved an issue that prevented record create or update actions from succeeding when the input included small decimal values these values were incorrectly rejected, even though they worked when submitted through the ui the system now properly handles small numeric values, including those in scientific notation, during record actions ssp import/export resolved an issue where attempting to export a package caused a maximum call stack size exceeded error this occurred when components had circular references, such as when component a referenced component b, which in turn referenced component a the fix now prevents duplicate processing of already handled components, allowing the export to complete successfully content library improved how publishing works when multiple users attempt to publish packages at the same time previously, a short lock timeout could lead to inaccurate attribution in the “createdby” field the lock duration is now configurable and set to 10 minutes by default, reducing the risk of conflicting updates and improving data integrity during concurrent publishing classic playbook re run timeout resolved an issue where re running a classic playbook through the api resulted in a timeout error the correct response is now returned, along with the expected run details, ensuring smoother re run execution via the api