May 2026 — Clearer flow debugging, scored quizzes, and safer editing

You can see why a visitor's flow stopped instead of guessing at the missing step. May also made scored quizzes easier to build with an AI assistant and addressed edits disappearing when another tab or assistant updated your project.

Find the decision that stopped your flow

The debugger now explains routing decisions in plain language, including questions skipped because they've already been answered, branches that didn't match, and score checks with no matching destination. Open Flows in the on-site debugger to follow the visitor's path and see what sent them down it—or stopped them from seeing anything. The debugger guide shows you how to inspect a flow while testing your website.

Enlarge

Debugger Flows panel showing the team assessment flow and its current question stepOriginalOriginal

Inspect a condition without leaving the canvas

Hover over a Condition node to read its rules without opening the editor. The preview makes it easier to check what separates the Yes and No paths while keeping the surrounding flow in view. See the Condition node reference for how those paths work.

Keep competing edits from silently overwriting your work

When an AI assistant or another tab changes your project, an idle editor picks up the newer draft rather than saving an older copy over it. If you have unsaved edits, the app keeps them visible and warns you before you reload; reloading replaces those local edits with the newer draft. Closing an unsaved question also asks for confirmation, whether you wrote it yourself or generated it with AI. Read about drafts and publishing for the distinction between your draft and what's live.

Build scored quizzes with fewer AI corrections

Your connected AI assistant can now create a question, its answer segments, and the points assigned to each answer together. Question creation preserves answer scores and visibility conditions, and flow-building tools reject steps that can't run after a form instead of accepting a broken path. Assistants also get clearer descriptions of branches that rejoin the main flow, and can update widget settings without resetting unrelated options. Connect your AI assistant to use these improvements.

Arrange form fields without them snapping back

Dragging a field into a new position now keeps it there in the form editor's Fields tab. Forms created through an AI assistant also start with an email field and submit button when no fields were supplied, and older forms missing those defaults become editable when opened. See form fields and layout for the available controls.

Enlarge

Form Fields panel with email and submit fields and the Add field button highlightedOriginalOriginal

Connect HubSpot and use your lists again

New HubSpot connections no longer fail because of mismatched authorization permissions or callback addresses. HubSpot contact lists now load in condition selectors, saved list references show their names, and form and flow actions can add contacts to the selected lists again. The HubSpot connection guide covers setup and syncing.

Smaller improvements and fixes

• Opening a question, flow, or widget without editing it no longer creates a spurious unpublished change.
• A connection warning now appears when live updates disconnect, with Retry and Dismiss controls, and disappears when the connection returns.
• Submitting a form no longer briefly flashes another flow step before the redirect.
• Flow reporting no longer loses question steps when multiple widgets share the same flow.
• WordPress post and category conditions now work on the first page view.
• New email-platform connections no longer fail because the selected provider was lost during setup.
• Long text sent to Customer.io is shortened to its supported attribute length instead of causing the whole request to fail.
• AI assistants can validate condition groups with four or more rules without an error and insert steps at the top level of a flow again.