Skip to main content
    Meet us at Open Source in Finance Forum (OSFF) New York, Convene Brookfield Place, November 4 to 5.Book a meeting
    Book a briefing

    Fluxnova 3.0: What Shipped, What Breaks, What To Do

    Reviewed October 2026

    Fluxnova 3.0 went GA in July 2026. It is the largest release since the FINOS fork, it modernizes the platform substantially, and it puts a major version migration in front of every existing user.

    New to Fluxnova? Start with Fluxnova: The FINOS Fork of Camunda 7.

    What shipped

    Platform modernization

    Fifteen library upgrades, including Spring Boot 4, for libraries that had reached end of life.

    Control Center UI

    Process definitions, heat maps, instance migration, incident retry, history, and DMN rule management with audit visibility into rule execution.

    Adhoc subprocesses

    Dynamic case management, where the steps are not declared in the model in advance.

    Restricted variables

    PII protection inside a process model.

    Plugin ecosystem

    Custom engine behavior including history data and authentication and authorization.

    MCP and agentic subprocesses, as plugins

    Processes exposed as tools invocable by LLMs and agents, and agents executing workflow tasks dynamically from prompts and business context. The release notes list both as custom plugins, not core engine features.

    What breaks

    Cockpit is replaced

    Control Center replaces the legacy Cockpit UI in 3.0. Anything built around Cockpit needs a new home.

    JBoss and WildFly

    Support was removed in version 3.1.1, released on 23 October 2026 (release notes). If you deploy on either, you have a forced move.

    Library surface

    Anything you have built against the pre-3.0 libraries needs retesting.

    Source: Fluxnova release notes on GitHub (FINOS), versions 3.0.0 and 3.1.1.

    THE PART TO WATCH

    Agentic adhoc subprocesses removed the control point.

    BPMN’s audit trail is trustworthy because every step is knowable in advance. A service task calls a system. A user task calls a person. The history is complete evidence precisely because nothing in it was improvised.

    An agentic adhoc subprocess declares nothing in advance and determines its steps at runtime. The engine records that it ran. It has no opinion on whether the agent was inside its authority, and there is no human task left where accountability used to attach.

    How Reign governs agent actions

    Common questions

    When was Fluxnova 3.0 released?
    July 2026, announced GA by the FINOS maintainers.
    Do I have to upgrade?
    Not immediately, but the direction is set. Control Center replaced Cockpit in 3.0, and version 3.1.1, released on 23 October 2026, removed JBoss and WildFly support, so anyone on those app servers has a forced move rather than a choice.
    Is Fluxnova abandoned?
    No. Version 3.0 is the largest release since the fork and the maintainers are active. The gap for a regulated institution is not code maintenance. It is having an accountable operator.
    What is an agentic adhoc subprocess?
    A subprocess whose steps are not declared in the process model and are instead determined at runtime by an AI agent, from prompts and business context.

    Talk to the team that runs the work.

    Reign Ops operates the platforms you deliver on, 24x7. Reign Factory and Reign Gateway are available today; Gateway is available on its own or included with Factory. Tell us what you are solving for and we will route it to the people who own that work.

    Book a briefing