limit of 400 concurrent Copy Data activities

• Hello AgustinPlain 
  
  Adding few other details in additiin to NandanHegde 
•  
• Fabric allocates computing resources through CU providing a different amount of capacity
• One Capacity Unit = two Apache Spark VCores for compute-intensive operations

• Capacity defines the ability of resources to perform activities or produce output, but does not directly control concurrency limits

• The 400-activity concurrent execution limit exists independently of your purchased capacity SKU

• Increasing your capacity from F64 to a higher SKU will provide more computational power but will not increase the 400 concurrent Copy activity limit

Potential solutiom would be :

• Implement staggered pipeline scheduling to ensure that not all Copy activities attempt to run simultaneously