What's New

The AI Builder now fully supports If/Else segment and operator edits.Users can add, remove, and update branches, segments, conditions, operators, and values directly through the AI Builder.

Key improvements include:

• Multi-level edits at the branch, segment, and condition level all work reliably
• Compound edits are handled in a single request, for example, adding a condition and changing an operator together
• Ambiguous requests on complex If/Else nodes now trigger a clarification prompt instead of failing silently
• Edit type and target identification has been improved, eliminating misclassification issues

What's New

The AI Builder now fully supports If/Else segment and operator edits.Users can add, remove, and update branches, segments, conditions, operators, and values directly through the AI Builder.

Key improvements include:

• Multi-level edits at the branch, segment, and condition level all work reliably
• Compound edits are handled in a single request, for example, adding a condition and changing an operator together
• Ambiguous requests on complex If/Else nodes now trigger a clarification prompt instead of failing silently
• Edit type and target identification has been improved, eliminating misclassification issues

What's New

The AI Builder now fully supports If/Else segment and operator edits.Users can add, remove, and update branches, segments, conditions, operators, and values directly through the AI Builder.

Key improvements include:

• Multi-level edits at the branch, segment, and condition level all work reliably
• Compound edits are handled in a single request, for example, adding a condition and changing an operator together
• Ambiguous requests on complex If/Else nodes now trigger a clarification prompt instead of failing silently
• Edit type and target identification has been improved, eliminating misclassification issues

Overview

Users could sometimes see 2 workflows created in the target location when loading workflows from a snapshot. This happened when duplicate workflow requests were sent at the same time, causing one workflow to remain in Processing while another completed successfully.

What’s changed

We've added a locks to ensure that when a workflow is loaded from a snapshot only 1 workflow is created for the same origin and location. This prevents duplicate workflows and avoids extra workflows getting stuck in Processing state.

Overview

Users could sometimes see 2 workflows created in the target location when loading workflows from a snapshot. This happened when duplicate workflow requests were sent at the same time, causing one workflow to remain in Processing while another completed successfully.

What’s changed

We've added a locks to ensure that when a workflow is loaded from a snapshot only 1 workflow is created for the same origin and location. This prevents duplicate workflows and avoids extra workflows getting stuck in Processing state.