Turbine On-Prem 25.1.5 Release

june 24, 2025 this release includes enhancements to existing features and addresses several issues identified in turbine cloud 25 1 0, improving both functionality and user experience addressed issues records record link for single select reference resolved an issue where reference record urls were not being generated correctly, which led to broken links and errors when attempting to access the records this issue has been addressed, and reference record urls now generate properly and function as expected record merging during environment slowness resolved an issue where, under conditions of slow network speed or environmental slowness, switching quickly between records could result in incorrect data being displayed previously, if a user clicked on one record and then quickly clicked on another before the first record fully loaded, the second record might display and save data from the first record this has now been fixed the application now properly cancels the previous request when a user selects a different record, ensuring that only the correct data is shown and saved in records co editing resolved an issue where co editing events were incorrectly triggered by real time updates previously, when fields like lists or checkboxes were updated externally, the frontend would publish co editing events as if the user had made the changes the fix ensures that co editing events are now only triggered when the user actively makes changes, ensuring a more accurate and consistent co editing experience with records globalrecordpatching resolved an issue where unmodified fields were incorrectly included in patch requests when the globalrecordpatching feature was enabled this behavior could lead to unintended data changes patch operations now only include fields that have been explicitly modified record update action resolved an issue where valid urls ending with special characters were incorrectly flagged as invalid during the update record action the validation has been updated to correctly allow such urls, preventing unnecessary urltextfieldformaterror messages record import from csv file resolved an issue that caused csv record imports to fail when timespan or url fields contained empty or null values imports now complete successfully even when these fields are left blank record updates resolved an issue where record updates did not properly enforce tracking id uniqueness, which could result in duplicate records being created under certain race conditions this has now been corrected to ensure uniqueness is maintained during updates history field resolved an issue where the history field would not display correctly when placed on a non default tab within a record previously, the history only appeared after the record was updated, causing confusion now, the history field consistently displays as expected regardless of which tab it’s placed on reports resolved a problem where scheduled report emails were delivered with blank or missing pdf attachments emailed scheduled reports now contain full, readable pdfs as expected fixed an issue where scheduled reports failed with a 400 error when accessing preview pdfs via the “download preview” option previews now load successfully from the schedule editor large text fields and attachments handling attachments previously, when large text fields were passed to a playbook (such as through a record event trigger), the attachment id used to reference the content was incorrectly replaced by the text itself this issue has been resolved, and the following updates have been made record create and upsert actions now allow selection and updating of large text fields large text fields are treated as string inputs for create and update actions for record search outputs, large text fields are returned as attachments note while large text fields can store up to 100mb, playbooks are limited to updating these fields with a maximum of 20mb due to action i/o constraints data loss during record patching resolved an issue where patching a record with a large text field could unintentionally overwrite the field's content, resulting in data loss large text field data is now preserved correctly during patch operations browser errors while reviewing large records resolved an issue that caused high browser memory usage when viewing records with large image attachments or extensive history fields this lead to browser crashes and "out of memory" errors performance and stability have been improved for handling such records ssp import/export resolved an issue with the ssp export from the library, which was caused by data inconsistencies due to mismatch in component ids resolved an issue where deleted components were still listed in the global export page, leading to export failures when an ssp import fails, the system attempts to roll back changes by deleting the imported content previously, if a playbook scheduled for deletion during the rollback was already missing (for example, if it had been deleted in the source tenant before export), a 404 error would occur this error obscured the original cause of the import failure, making debugging more difficult the system now continues the rollback process even if such content is already missing this ensures that the original import error is preserved and clearly displayed in the logs and user interface, improving traceability and debugging webhooks resolved an issue where events from all webhooks were shown in the webhook events tab, which could cause confusion during troubleshooting this issue has now been fixed, and the tab now correctly displays only the events associated with the specific webhook being configured reports resolved a problem where scheduled report emails were delivered with blank or missing pdf attachments emailed scheduled reports now contain full, readable pdfs as expected bulk edit resolved an issue where bulk edit notifications were not displayed upon job completion, and report contents were not automatically refreshed now, a real time notification is shown when a bulk update finishes, and the associated report refreshes automatically to reflect the latest changes bulk edit and delete actions were previously controlled by report level permissions, which resulted in unintended access for certain roles this behavior has now been corrected—bulk operations require record level permissions and explicitly need update record or delete record, along with lock record this change aligns with the intended application level permission model user roles and groups resolved an issue where internal admin users were unable to assign roles or groups to disabled external users when the " invite external users " setting was turned off admins can now update roles and groups for these users allowing them to pre configure users with the correct permissions performance and resiliency improvements improved the resiliency of turbine agent when creating container actions previously, if the container engine was unreachable or unresponsive, jobs were immediately marked as failed now, the system will retry connections a configurable number of times before failing, ensuring better handling of transient errors and reducing unnecessary job failures report and dashboard slowness resolved an issue where default reports were loading slowly and the ui became unresponsive due to delays in the api call reports now load within expected timeframes, and the ui remains responsive during the process canvas ui flickering resolved an issue where the ui flickered when rendering playbooks containing a large number of flows components now wait for all data to fully load before rendering, providing a smoother user experience export record action resolved an issue where field values in export record actions were mismatched or incorrectly formatted because of column and row misalignment during playbook execution this has been corrected to ensure data exports are accurate and properly formatted known issue inconsistent sorting of playbook runs issue the playbook runs page may display runs in an inconsistent order by default the latest run is not always shown at the top, which can make it difficult for users to quickly identify the most recent execution workaround click the “start” column header in the playbook runs table to manually sort the runs by start time this will correctly order the runs with the latest at the top or bottom, depending on the selected sort direction