Hello Ram Sekhar Grandhi,
I'm not sure the reason why two loops are specified even if Outlook connector de-batches bunch of mails. Anyway, there are following workarounds as of now.
(1) If you accept sequential processing of mails, could you please disable "Split On" property? Even when two loops exist, the flow should work.
(2) If you like to process mails in parallel, could you please remove the outer loop? And for_each
parameter should be changed from @item()?['Attachments']
to @triggerBody()?['Attachments']
because this flow processes each mail.
Also, appropriate "Split-On Tracking ID" is helpful for tracking each de-batched instance. Here is an example, where "id" in each mail is used as "Split-On Tracking ID". This is an optional configuration, so the flow works even if you leave Split-On Tracking ID brank.