---
title: "Release Notes: BluBees.ai v4.1.0 - Beta - August 2026"
canonical: "https://doc.blubees.ai/space/blubeesdoc/183631873/Release%20Notes%3A%20BluBees.ai%20v4.1.0%20-%20Beta%20-%20August%202026"
format: markdown
---
> Macro (toc)

| Field | Detail |
| --- | --- |
| Version | 4.1.0 |
| Release Date | August 2026 |
| Status | [Live Beta Production Rollout] |
| Target Audience | Beta Cohort & Enterprise Design Partners |

> ℹ️ Welcome to the BluBees.ai Version 4.1.0 Beta update. This release introduces visual step execution status, a Forge runtime upgrade, flow variables, array splitting, and enhanced response processing control for OnResponse steps.

## New Features & Enhancements

### Step Execution

The flow-designer Node UI now visually displays execution status for each step — success, failure, running, and other states — right on the node, so you can track flow progress at a glance.

- **Inspect execution details** directly from the node, without leaving the flow canvas.
- **Integration status visibility** on the node — see whether a connection is connected, synced, or in an error state.

### Forge Runtime Upgrade

Upgraded the Forge Runtime from Node.js 22 to Node.js 24, bringing the latest performance improvements and long-term support.

### Flow Variables

Introduced flow variables to let you store and reuse field values throughout a flow.

- Manage variables from a new dialog, launched directly from the current flow in the flow-designer.
- Define, save, edit, and delete variables as needed.
- Variable names must be unique (name matching is case-insensitive).
- The field-mapping screen now includes an option to select and insert flow variables into the field list on either side of a mapping.
- Flow variables are scoped to the entire flow — available for field mappings across every step, but limited to a single flow execution.
- Store a field value against a variable name during execution, then reference that variable in field mappings anywhere else in the flow.

### Array Splitter

You can now add an Array Splitter node to any flow to process array-type fields item by item. Point it at an array field (via a simple field picker or JSONPath), and it routes each item to a node of your choice while triggering a separate completion step once every item has been handled.

- Choose **Sync** mode to process items in order, or **Async** to run them in parallel.
- A **"Continue on error"** option lets you decide whether one failed item should stop the whole batch or just get skipped and allow the flow to proceed.

### Response Processing for OnResponse Steps

BluBees flows now support explicit control over how OnResponse steps handle incoming responses — as either **Async** or **Sync** operations.

#### What OnResponse Does

Every BluBees flow starts with exactly one inbound trigger and continues through a chain of reactive steps. The two event types work differently:

- **WebTrigger** — used on the first step of a flow. It is an inbound webhook: BluBees listens for an external system (e.g. TestRay) to call it. Nothing happens until that outside call arrives.
- **OnResponse** — used on every step after that. It fires the instant the previous step's CALL returns a response. No external system is involved — it is BluBees reacting to its own prior action completing.

| Application Side | Event Type | What It Means |
| --- | --- | --- |
| Target (the app this step acts on) | CALL | Actually perform the action (create branch, copy file, trigger pipeline, etc.) |
| Source (the app that starts this step) | OnResponse (Synchronization) | Begin this step as soon as the previous step's call comes back |

This is what makes a flow run end-to-end without anyone clicking anything after the initial trigger — each step's completion is what starts the next one.

#### What's New: Response Processing (Async / Sync)

Previously, an OnResponse step always started the moment the prior step's response arrived, with no control over how that response was handled. **Response Processing** now gives you that control directly:

- **Async** — the flow continues immediately without waiting for this step's response to be fully processed. The step handles its response independently, in the background.
- **Sync** — the flow pauses at this step until the response has been fully processed, and only then proceeds to the next step.

> 📝 **Async is the more scalable, production-safe default** — reach for Sync deliberately, only where step order and completion genuinely need to be guaranteed.

## Bug Fixes

- **Visual Conditional Builder** — Fixed an issue where a saved SpEL expression did not render correctly in the builder.
- **Field Mapping** — Fixed an issue where the last saved field mapping value was incorrectly being retained when configuring a new field mapping.

## The Roadmap: What's Next?

As we progress through the Beta version upgrade phase toward our full General Availability (GA) launch, our engineering teams are actively building features that will **automatically discover your enterprise tech stack and map out recommended configuration flows** across all your business tools simultaneously.

> ℹ️ **Beta Feedback Channel:** Found a bug or have a feature improvement suggestion? Reach out via the [Support portal](https://blubees.atlassian.net/servicedesk/customer/portal/1). Stay tuned for what's next.