Nested namespace declarations are not handled correctly by Camunda BPMN editor

We are using Camunda web-based modeler version 5.0.5 for editing BPMN diagrams stored and executed via Flowable. So there is the Flowable namespace in the definition. We also added our own custom tags (“customextension”) like this:

<?xml version="1.0" encoding="UTF-8"?>
<definitions xmlns=""
  <process id="myid" customextension:mytag="myvalue">
    <startEvent id="start" flowable:sometag="somevalue"/>

This works fine so far: when editing via Camunda, both customextension and flowable tags are preserved when saving back to the Flowable service.

However, it goes wrong when I change the to this:

  <process id="myid" xmlns:customextension="" customextension:mytag="myvalue">

While this is valid XML as far as I know, Camunda throws this error:

missing namespace information for  flowable:expression = something 

Does anybody know what might be wrong here?

Note: I previously posted this message on

Hi @erikvoorbraak, welcome to our forum!

We’ve fixed a few issues related to exporting of nested XML documents in v6.5.1. Could you double check the problem persists in the latest version of our toolkit?

If you provide me with a broken diagram that contains DI information I’d be able to look into the issue myself, too.