Turbine Cloud 26.3.0 Release

turbine is evolving into a powerful automation platform that combines intelligent development, enterprise grade controls, and operational scale in one experience with hero ai now capable of making coordinated changes across multiple flows, richer management experiences for playbooks and ai agents, flexible identity management, time based automation, more precise data retrieval, and built in safeguards for application scale turbine is moving beyond simply helping teams build automations, it is helping them build faster, manage complexity, and confidently scale automation across the enterprise what's new in this release? playbook generator edit multiple flows in a playbook the hero ai playbook generator agent can now edit multiple flows within a single playbook in one request select the flows you want to change through the canvas ui or describe them in natural language, and the building agent applies coordinated edits across those flows this makes it faster to build and maintain multi flow playbooks without switching between flows and prompting the agent separately for each one for more information, see create and modify playbooks with hero ai docid\ tmmnjglc0e9lipo37kzpb enhanced list experience for playbooks, components, and ai agents the playbook, component, and ai agent list pages have been redesigned to make searching, navigation, and content management easier the new experience brings these pages in line with the operational health experience and surfaces more useful information directly in the lists, helping users quickly find the content they need and understand what they are working with for more information, see playbooks overview docid\ dp agnnne2mjjfgtv2lz5 , components docid\ c7ipcs5ndr9sgu4z6pjs0 , and ai agents in orchestration docid 4er81s1tgemt4h2rvruaw support for multiple sso identity providers per account turbine now supports multiple sso identity providers within a single account, allowing organizations to authenticate users through multiple saml providers, including azure ad, okta, ping, and google account administrators can configure and manage multiple identity providers, test saml connections, and associate users and groups with the appropriate provider multiple directory services are also supported, making this especially useful for mssps, organizations with multiple business units, and environments that use separate identity sources this gives administrators greater flexibility to align turbine authentication with their existing enterprise identity architecture multiple sso is currently available behind a feature flag contact swimlane support to enable it action required — idp signing certificate starting in turbine 26 3 0 , every saml sso configuration must include a valid identity provider (idp) signing certificate this requirement applies to all saml configurations — including accounts that use a single identity provider — and is not limited to multi sso existing user logins continue to work if a configuration does not yet have a certificate you cannot edit or save an existing saml configuration until you add a valid idp signing certificate new saml configurations require a certificate before they can be saved saml response signature verification is always enforced and cannot be disabled upload the idp public signing certificate under identity provider settings for each saml configuration supported formats include pem and cert for steps, timeline, and faqs, see enable saml for sso docid\ irgxchuyjmsyplqdq3duh for multi sso setup, also see directory services docid\ kygdtejblyxawquk65iza , users docid\ iuzidcollvgz3x8qj4ywj , and customize your user profile docid\ prwh3nd3y3c7jl5ohbvh1 sort direction in search records and export records native actions the search records and export records native actions now support explicit sorting by tracking id, including ascending and descending order previously, playbook authors could filter, select fields, and limit results, but had limited control over the order of returned records this often required retrieving additional records and reordering them using transform data or scripts with configurable sort direction, playbooks can retrieve records in the expected sequence directly from the action—making data processing more efficient, particularly for high volume and ai soc workflows for more information, see search records docid\ jche lec5pryean7hjgbg and export record docid 8v36yz2nl8b89i5amxlhr trigger playbook flows at a specific time turbine can now trigger a playbook flow at a specific time based on a date/time field value configure a date/time field with an optional delay and select the playbook and flow to run when that time is reached turbine automatically creates the trigger and starts the selected flow at the calculated time this capability introduces the foundation for sla driven automation , allowing workflows to take action based on when something is due additional sla capabilities, including an sla field, are planned for future releases this trigger is configured through the date/time field and is not available as a standalone trigger when building a new automation in canvas for more information, see triggers docid\ sedgthtxrzuohzsuvhad4 and select fields and assign field properties docid\ fngazwp7nqsnvsudl8nbh application builder configurable field limit and monitoring application builder now provides configurable field limits and real time visibility into field usage, helping protect platform performance and elasticsearch indexing as applications grow administrators can define a maximum number of fields per application at the tenant level, with a default limit of 500 builders can see their current field usage directly in application builder—for example, 320 / 500 —as they add or remove controls if an application exceeds the configured limit, turbine prevents the application from being saved and clearly explains how to resolve the issue this gives administrators greater control over platform scale while helping builders understand and manage application capacity as they design for more information, see application builder docid 6q6y4 02l v2khn80gmo5 and tenant system settings docid\ roqfi96efojbqstjig2qt addressed issues canvas operational health showed runs whose data was already purged fixed an issue where playbook and component runs older than the 14 day io data retention period still appeared in operational health but could not be opened because their trigger data had been pruned runs past the retention period are no longer returned in operational health nested loop error showed multiple actions as failed fixed an issue where a failure in a loop inside another loop caused the playbook runs page to show all actions in the run as failed when only one had failed the run now shows only the actions that actually failed loop retry success still marked the loop as failed fixed an issue where a task inside a loop that failed and then succeeded on retry still marked the overall loop or component as failed loop and run status now reflect a successful retry instead of treating the earlier failed attempt as the final result script action returned wrong values for negative indexes on nested lists fixed an issue where the script action returned incorrect values for negative indexing into nested structures such as lists of lists or lists of dictionaries (for example, 1 returned the second to last item) negative indexing on nested lists now returns the correct values create variables stored a cleared array as null fixed an issue where clearing the value of an array variable in the create variables action stored it as null instead of an empty array, causing downstream counts to be off by one cleared array variables now remain an empty array search records returned nothing when the application was set dynamically fixed an issue where the search records native action returned no records when the application was selected dynamically through a playbook property instead of being hardcoded search records now returns the expected records when the application is set from a playbook property action description failed to save with a colon or special character fixed an issue where entering a colon or certain special characters in an action description produced a yaml parse error and did not persist the change, even though a success message appeared action descriptions with colons and special characters now save correctly ungrouping a component did not update transformation references fixed an issue where ungrouping a component did not update the expression references in transformation blocks, leaving stale references transformation references are now updated correctly when you ungroup a component connector test input was not cleared when an input was deleted fixed an issue where deleting a custom input used in the connector test panel left the input value in the test request even though it was no longer visible in the ui deleted inputs are now removed from the test request independent component failures were missing from operational health fixed an issue where a component that succeeded but was then timed out by its parent playbook was recorded inconsistently, so an independent component failure could be missing from the operational health page component run outcomes now appear consistently in operational health records rich text and comment cursor jumped to the start during co editing fixed an issue where the cursor jumped to the start of a rich text or comment field when a co editing update from another user arrived while you were typing the cursor now stays in place when co edit updates come in comment being edited was lost when another user posted a comment fixed an issue where text you were typing in an existing comment was erased when another user saved a new comment on the same record, forcing you to retype it in progress comment edits are now preserved when other comment updates arrive conditional formatting colors were not applied to all columns fixed an issue where conditional formatting color patterns were not applied consistently across all columns on application records conditional formatting colors now apply correctly across all columns content library / ssp importing one invalid playbook failed the entire import fixed an issue where importing an ssp failed the whole batch when a single playbook failed validation, and the platform did not identify which playbook was invalid valid playbooks now import successfully and the invalid playbook is identified unable to pull content from a remote git repository fixed an issue where a content library remote git repository remained locked after validation, so customers could not pull content from the remote content library git integration no longer leaves the repository permanently locked, and pull from remote works as expected connectors graph api test connection reported failure for valid credentials fixed an issue where test connection for a graph api asset returned a failure (for example, 403 forbidden) even when the oauth credentials were valid and real actions succeeded test connection for graph api assets now reflects actual connectivity