We have had Camunda running for approximately one month.
After doing some refactoring and tidying in the project, we renamed the root package in the project from “cmp” to “workflow”.
This resulted in today the Camunda workflows not being able to progress, because the class path is using the old package.
The new one
For new instances with the newer version of the workflow, it is working ok.
However older versions are still referring to the older classpath and cannot progress, the server throws a 500 error.
The diagram has not changed apart from the service tasks paths.
How can we hack this to work again?
We tried adding back a package called
cmp however because it is in a different root to spring-boot, the dependency injection will not work in that scope.
Is there a way to hack the instance in the database?