Duplicate run of integration flow consuming event from event mesh of SAP Cloud Integration Suite

[SumitKundu]

Hi,

I have a doubt related to event message consumption in SAP Cloud Integration. I am consuming an event topic configured in Event Mesh capability within SAP Integration Suite.

And created a topic subscription in the above queue. This event is sent from S/4HANA Cloud system when a sales order item is changed.

I am consuming the event in Cloud Integration process using AMQP sender adapter

Now when a sales order item is changed in SAP S/4HANA Cloud, I see the iFlow is triggered successfully but there always are two runs in the log:

Also the queue in event mesh is not cleared even after successful completion of the message in cloud integration process consuming the event.

1. Why is it triggering two runs of the same consumer integration process?

2. Why is the queue not getting cleared after integration flow completes.

Best regards,

Sumit

[SumitKundu]

Hi @ajmaradiaga, Would you please take a look at this?

[ajmaradiaga]

In Cloud Integration you should be consuming from the queue directly, not subscribing to the topic. The queue is already subscribed to the topic and it will capture those events for you. This is why you received the events in Cloud Integration (because of the additional topic subscription) but the queue still has events. You are not consuming the events in the queue. In the sender adapter, configure the queue instead of the topic and it should work.

[SumitKundu]

Thanks @ajmaradiaga again for helping out. Changing the AMQP sender adapter to queue instead of topic resolved the issue 2. Regarding issue 1 of duplicate runs of the iFlows, I realized two worker nodes are running as the screenshot shows 2 different instance ids for the runs in MPL. I thought one worker node should stop processing the message once it realizes another worker node is already processing it as mentioned in this note. However this note (https://me.sap.com/notes/2582931/E) talks about integration triggered using a timer, is it not applicable to integration processes triggered by AMQP sender adapter?