Turbine Cloud 26.3.3 Release

Turbine Cloud 26.3.3 delivers a hotfix addressing issues identified in Turbine Cloud 26.3.2.

Addressed Issues

Application Builder Blocked Save After Upgrade When Flows Were Shared — Fixed an issue where Application Builder blocked save after upgrade to 26.3 with the error Duplicate flow assignments across triggers when two playbook buttons, or a playbook button and correlation, already used the same flow. Playbooks continued to run. You can save those applications again. A DateTime field trigger still cannot share a flow with another trigger. For more information, see TriggersTriggers.

Search API Returned Unusable Reference Field Values — Fixed an issue where the Search API returned raw stored values for reference fields instead of the referenced record ID, application, and tracking label. Integrations that search records with a personal access token now receive the expected reference field data.

Connector Action Stability Enhancements — Improved stability for connector actions during playbook runs. Connector actions now run more reliably.

Action Properties Opened Empty or Dropped Required and Sensitive Settings — Fixed an issue where opening an action, including Update Variables, hid inputs or dropped Required, Sensitive, and Type settings when schema references were missing. Canvas now restores those properties and prompts you to review highlighted settings before you apply. Playbook and component runs are not changed. For more information, see Configuring PlaybooksConfiguring Playbooks.

Copied Loop and Parallel Actions Lost Mappings or Shared Configuration — Fixed an issue where copy and paste, including actions inside Loop or Parallel, and some solution imports left actions sharing configuration or dropped input mappings. Copied and imported actions now receive their own configuration, and mappings remain on the pasted actions.

Copied Actions Are Omitted From Configuration Review After You Pause Recovery — If you pause configuration review (Cancel, Skip, or leave the review) and then copy an action or a flow that still needs review, later review repairs only the original action. The pasted action keeps mappings but is omitted from the review list, and Save keeps that incomplete state. Workaround: Finish the review on the original action before you copy. If you already pasted, delete the pasted action and copy again after the review is complete. For more information, see Configuring PlaybooksConfiguring Playbooks.

Configuration Review Can Open After Hero AI Creates a Playbook — After you create a playbook with Hero AI, Canvas can open Configuration details need to be reviewed. This does not happen for every generated playbook. Complete the review on the flagged actions, then save. Workaround: Follow the configuration review. The dialog can also clear on its own after about an hour. For more information, see Configuring PlaybooksConfiguring Playbooks and Create and Modify Playbooks with Hero AICreate and Modify Playbooks with Hero AI.