Inbound RabbitMQ connectors still duplicating subscriptions despite manual deduplication settings in Camunda 8.5.25

Community Community Extensions
1

Hi everyone :waving_hand:,

I’m running a self-managed Camunda 8.5.25 environment and running into an issue where manual deduplication for RabbitMQ inbound connectors doesn’t seem to work as expected.

:puzzle_piece: Environment Details

Component Version
Camunda Platform 8.5.25
Zeebe Engine 8.5.25
Connectors Bundle 8.5.22
RabbitMQ Connector io.camunda:connector-rabbitmq-inbound:1 (v8.5.22)
Camunda Modeler 5.33.1
BPMN Schema BPMN 2.0.2 + Zeebe extensions

:gear: Context

I have several inbound RabbitMQ connectors defined within the same BPMN process (a mix of message start and intermediate catch events).

All these connectors:

  • Use the same authentication.uri and queueName

  • Have

    <zeebe:property name="deduplicationModeManualFlag" value="true"/>
<zeebe:property name="deduplicationMode" value="MANUAL"/>
<zeebe:property name="deduplicationId" value="adf060c58b21"/>

  • Differ only in their activationCondition (e.g.
    message.body.name = "featured_jobs" vs "application_decision")

  • Are in the same BPMN diagram and process definition

  • Have mutually exclusive activation conditions

Based on the documentation, this setup should result in one shared RabbitMQ subscription (single consumer group), since all inbound connectors share the same business properties and deduplication ID.

:police_car_light: Problem

After deploying the process:

  • Multiple RabbitMQ consumers are still created (one per inbound connector)

  • The Camunda Console shows duplicate inbound connector instances

  • RabbitMQ itself confirms multiple active consumers on the same queue

:red_question_mark: Questions

  1. Does Zeebe 8.5.25 with Connectors 8.5.22 fully support manual deduplication for RabbitMQ inbound connectors?

  2. Which specific connector properties must be identical for deduplication to merge inbound subscriptions?

  3. Does the activationCondition or BPMN element ID affect deduplication grouping?

  4. Are there any known issues or workarounds for this behavior in the 8.5.x line?

Any insight or configuration examples from the Camunda team or anyone who has resolved a similar issue would be greatly appreciated

2

Hey @robert_njuguna

Thank you for reaching out, and for the detailed question :slight_smile:

Deduplication is available starting from 8.6, so you would need to upgrade if possible.

Let me know if it helped,

Jonathan