Encountering an issue when using the Notify action inside a for-loop (Under parallel) in a compound action flow. The Notify action is configured with two interactive buttons: Approve and Reject, and is used to send actionable notifications to users.
When the loop processes a larger list (10+ items), users do not receive any notifications. Instead, the conversational flow appears to stall, and the user continuously sees the response:
“Fetching invoice details for your pending approvals…”
In contrast, when the list contains a smaller number of items (typically fewer than 5), the Notify action works as expected and notifications are successfully delivered to the user with the approve/reject options.
There are no errors or failures visible in the logs during execution. The workflow does not explicitly fail or terminate; rather, it seems to hang silently once the list size crosses a certain threshold. This makes it difficult to identify whether the issue is related to rate limits, payload size, interactive button handling within loops, or an internal constraint on Notify actions.
