An Azure managed MySQL database service for app development and deployment.
Thank you for the feedback and apologies for the late response.
Yes all the tables in the ForEach start running at the same time. And yes this happens for the bigger tables. But strangely, when I receive the error and I end up not making any changes, all the tables will run as normal and successfully the following day. So I am trying to understand why we get the error and how to prevent it.
I have created a copy activity for a big table and have tried to run it, it runs successfully without giving me any error that is of course if I set a big timeout for it.