I am using the Kafka Start Event Connector in a process, followed by a user task. When I create a message on the topic used by the Kafka Start Event Connector, it results in 2 tasks in tasklist. I can’t see any configuration difference in another process using the same connector so, I am not sure why this is occurring. Anyone seen this before and know a resolution?
Hi, and welcome to the forums!
A common cause of this is accidentally having two connections from the Start Event to the first task. If you post your BPMN, the community will help you check for that.
Thanks for the reply. It is a very simple process I created as a mockup to get user feedback before fleshing out for the full process. I have attached the BPMN and would appreciate any feedback.
Repayment Reconciliation.bpmn (5.9 KB)
I’m not seeing anything obvious in the BPMN that would cause two tasks.
Are you getting two tasks, or two process instances?
Just checked. I am getting 2 process instances.
Do you potentially have two deployments (slightly different versions of the BPMN) that might both be listening to the same message but with different process definition IDs?
No, this is the first deployment (v1)
Is this the same issue?
Looks like it might be, but I’m only another user like you, so I can’t really confirm it.
Do you have more than one connector runtime running in your environment?
1 Like
It was that issue. The 8.5.5 connector update for the cloud version contains the fix. I applied the update on our dev system and updated the Kafka Start Event Connector in one of my processes and I didn’t get 2 process instances started. I will apply to my other process now.
Thanks for helping out with this issue.
1 Like
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.