@Johns-305 Thanks for reaching out. This is an expected behavior as documented here. The exception to the default behavior are nested loops where iterations always run sequentially, not in parallel. Therefore, the Concurrency control has been removed from the nested loops.
The exception to the default behavior are nested loops where iterations always run sequentially, not in parallel. To run operations in parallel for items in a nested loop, create and call a child logic app.
The workaround will be to run operations in parallel for items in a nested loop, create and call a child logic app.
Let me know if you have any queries or concerns.