April 2026 Product Club | Mozart Orchestrator's Split and Merge Feature for Parallel Process Execution

Welcome to the April Product Club Recap!
This month, we went deep on one of the most practical upgrades to hit Mozart Orchestrator: Split and Merge. Nishikanth N, Director of Product Management, walked us through what the feature does, why it matters, and how it fits into the bigger picture of agentic process automation. Max Cassidy, Senior Developer Evangelist, brought it to life with a live demo that showed just how much time and complexity you can shave off when you stop forcing parallel logic into a sequential line.

If you were unable to attend, here's everything you need to know, plus the recording so it'll be like you didn't miss a thing:

First, a Quick Reset: What Is Mozart Orchestrator?
Nishikanth opened with something that reframed the whole session: a grounding on what agentic process automation actually means, and where Mozart Orchestrator fits in.

The short version is this. Automations handle discrete, repeatable tasks. Processes coordinate those automations, along with people and systems, end to end. AI agents use reasoning to decide which tools to use and when. And agentic process automation is what happens when all three come together. Nishikanth was clear that agents don't replace automations, they elevate them, using them as tools within a broader, goal-driven flow.

Mozart Orchestrator is the layer that makes all of this work at scale. It's been significantly enhanced from what many of you may remember as Process Composer, with a redesigned canvas, improved observability, and support for bots, API tasks, AI agents, document processing, and human-in-the-loop steps, all in one place. The platform has seen more than 90% year-on-year growth in customers using it as their path to agentic process automation.
And yes, if you already have Process Composer processes built, they carry over automatically. Nothing to rebuild.

The Core Problem Split and Merge Solves
Most real-world business processes were never meant to be sequential. But until now, developers had no choice but to build them that way, squeezing parallel logic into a single line, stacking workarounds, and watching maintenance complexity grow with every change.

Split and Merge changes that. Now available in version .39 (currently rolling out to cloud customers), it lets you model and execute parallel branches within a process, so independent tasks run at the same time and converge at a single merge point when complete.
The key capabilities:

• Split lets you create multiple parallel branches that execute independent steps simultaneously.
• Merge automatically waits for all branches to complete before the process moves forward. No custom logic or manual tracking required.
• Branches can be set to always run or run conditionally, with at least one fallback branch required when using conditions.
• Nesting is supported, so you can run split and merge blocks within each other for more complex flows.
• The platform has been tested and certified for up to 10 branches, though more are supported.

Nishikanth walked through an employee onboarding demo that made the design click: instead of running payroll setup, Workday profile creation, and IT access provisioning one after another, all three branches ran in parallel. The process only advanced once every branch had completed.

Max added his own take with a chef analogy that honestly nailed it: you wouldn't cook the steak, then the vegetables, then the fries one at a time. You'd have three cooks working in parallel and plate everything together at the end. Same idea here.

Live Demo Highlights
Max demonstrated a lighter version of the same pattern, using a parallel process to add employees to an org chart via API task while simultaneously triggering desktop automation to send onboarding emails. Both branches kicked off at the same time, both finished, and the process moved on. Clean, fast, and easy to follow.
A few things worth noting from the demos:

• Drag-and-drop from the elements panel is all it takes to add a split and merge block to your canvas.
• Each branch gets its own named description, conditions, and series of steps.
• The canvas supports swimlanes (vertical or horizontal), a minimap for large workflows, full-text search across both the canvas and property panels, and search-and-replace.
• Copilot for Automators is available for natural-language process building, as part of the Automator AI package.

What's Available Now and What's Coming
A few important markers for teams evaluating or actively building:
Available now (v3.9): Split and Merge for Enterprise license customers on cloud. Full parallel execution, nested branches, conditional logic, automatic merge point handling, and rich observability including live monitoring and detailed process history.
Coming in v4.0: API and webhook-based triggers so processes can be kicked off by external events, including out-of-the-box triggers and Universal Listener webhooks.
On the roadmap: End-to-end process simulation and testing, AI-powered process optimization recommendations, branch exit post-processing logic, conversational dashboards (ask questions in plain language, get live process insights), ETL functions within Mozart, and expanded AI governance controls.
Licensing note: Mozart Orchestrator is available to all Control Room customers. Split and Merge specifically requires an Enterprise license. If an Enterprise license is downgraded or terminated, affected processes remain intact but parallel branches will execute sequentially, ensuring compliance and continuity.

Session Q&A
Q: If we have existing processes built in Process Composer, will they automatically convert to Mozart Orchestrator?
A: Yes. No action needed. Existing processes carry over automatically and immediately benefit from the new canvas, swim lanes, and other enhancements. Split and Merge will also be accessible as long as you have an Enterprise license.
Q: Is Mozart Orchestrator available on a base license, or does it require an upgrade?
A: The core capability to create and run processes is available to all customers with Control Room access. Split and Merge is an Enterprise-only feature.
Q: If three branches are running on the same server, how are shared resources (like Excel or Word) managed?
A: Branches that include task bots require bot runners. If your device pool has three devices and you have four branches, three run in parallel and the fourth queues efficiently. Branches that use only APIs, forms, or AI agents do not require additional runners and will always execute in true parallel.
Q: Can Mozart Orchestrator be triggered via API?
A: API and webhook-based triggers are coming in v4.0, later this month. This will include out-of-the-box web triggers and the ability to create webhook triggers via Universal Listeners.
Q: Is Split and Merge available in Community Edition?
A: Mozart Orchestrator is available in Community Edition. Split and Merge is only available with an Enterprise license.
Q: In Merge, can we compare the status of all parallel steps, or do we need individual variables to track each branch? A: Post-processing nodes at branch exits are on the roadmap and will support this natively. In the meantime, you can add a task bot or API step just before the branch exit or just after the merge point to collect and compare branch outputs.
Q: How does WLM queue priority interact with process-level bot steps?
A: Priority settings on task bots are respected regardless of whether the trigger comes from a process or a standalone WLM queue. Note that WLM capabilities don't apply to processes themselves, but any shared bot runners will honor the priority you've configured.

Swag Winners
As always, we randomly selected some lucky winners from our engaged audience. Congratulations to:

• ​@megha.pai 
• ​@dgabbad369 
• ​@Havva

Get Hands-On

If this session got your wheels turning, here's your next move: join us for the Developer Meetup + Product Club Mashup on April 23rd, where you'll actually build parallel automations with Split and Merge. This is the hands-on companion session to everything you saw during this session.

We'll see you there.