Camunda start process instance with specific version of workflow

Camunda 7 Topics Discussion & Questions
1

Hi, We are running camunda 7.11 version . We have got multiple bpmn workflows deployed and each of them has too many versions running (say like more than 1000 versions for each bpmn workflow). When triggering start process instance using this REST API , camunda servers are hanging up.

Below are the questions i have got for the given scenario mentioned above

  1. When i trigger the start process instance by using process definition id , why it is always checking for all the versions of that particular bpmn workflow (which leads to huge increase in the memory/cpu utilization and the server hangs/crashes )
  2. Is there any way to avoid such above mentioned scenario in question 1, means when i want to trigger a start process instance it should only start the process instance with respect to particular version and not look up for the previous running versions?
  3. Is there a way to pass specific version number of the workflow while making this api call?
2

Hi @aniinprni On BPMN level you have a property called as “Binding” if you select “latest” from the List of Values ideally it should pick the latest deployed version of that BPMN.

Best practice is to select “latest” so that your latest changes are always picked up. In the same tab there is an option called “version” you can specify specific version of that workflow also which will be always invoked when you trigged the Workflow.

Once you make changes in “Binding” you must deploy your BPMN for it to take effect.