Duplicate run of integration flow consuming event from event mesh

[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

[Ryan-Crosby]

The two runs is likely multiple runtime nodes and I would imagine the queue isn't cleared if your QoS is set to require acknowledgement of the message, but has not been sent.

[SumitKundu]

@Ryan-Crosby Thanks for the response. I am using Event Mesh of Integration Suite. Can you please clarify where the queue setting is 'set to require acknowledgement' ?

[Ryan-Crosby]

I cannot see your photos because they are tiny, but I would recommend reviewing this blog that covers AMQP. https://community.sap.com/t5/integration-blog-posts/cloud-integration-connecting-to-messaging-system...

[emreanil]

Hi Sumit,

[emreanil]

Hi Sumit, I have the same problem for two weeks. Might it be an SAP bug? Same published event is triggering for two times. Did you find a sloution?

[SumitKundu]

Hi @emreanil, well in my case event published only once from S/4HANA Cloud, there is no issue in event publishing. The issue was at the event consumer side, i.e., two separate worker node instances of SAP Cloud Integration was processing the event at the same time. I did not get any solution for that. For the second issue that I mentioned in the question was resolved by using queue name like queue:<your/queue/name> instead of the topic.

[emreanil]

Hi @SumitKundu,

[emreanil]

Hi @SumitKundu, In my case I had the same issue. There was 2 trigger on my flow with same event id.I couldn't understand why but it seems like it is not happening anymore. Maybe it was a SAP bug. Thank you for answer.