Multi engine / shared database


I am investigating Flowable at the moment and was wondering if this scenario is supported:

We want to deploy multiple applications with each application having it’s own engine and processes which are stored in 1 database.

We want each application/engine to have it’s own asynch executor (job scheduler) running.

Could we use the tenant functionality to support this scenario? Can we configure the async task executor in such a way that only jobs of a specific tenant (which is in my case a flowable engine) are selected and jobs of other tenants (which should be picked up by another engine) are ignored?

With kind regards,


That would be interesting for me too. It would be a nice feature for doing canary deployments, e.g. in Kubernetes, so that the Job Executor of the canary instance (Pod) is aware of a specific bpmn deployment - for making sure, that after going live, my changed bpmn is working well together with my changed application code

Hi Arnoud,

The feature is supported (multitenancy deloyments)

Each engine can have its own executor.

Try ExecutorPerTenantAsyncExecutor


Hello, I’m a novice. I want to know if I can set the global tenantId at this Multi engine / shared database scene.I use the flowable-spring-boot-starter-process-rest.So I don’t have to pass tenantId param in each api calls.
thank you very much! :grinning:


Do you need global tenant id for process instance start? (to look for process definitions in the global scope…)

Thanks for you reply. I have two services build with flowable-spring-boot-starter-process-rest,and each service has its own processEngine but share the same I want use tenantId to achieve Multitenancy.
When I call serviceA rest API,I must pass the tenantId param of serviceA.So,Is there any way to config a init tenantId for processEngine of serviceA?
Best wishes! :smile:

The short answer is no. Both engines can handle requests for both tenants. If you put load balancer in the front of rest service you can split requests, but it is outside of flowable-engine.

OK,I understand.Thank you for your patience.
Best Regards