A Copy activity that sits in queued state is rarely a random Azure Data Factory issue. It is usually a capacity, connectivity, or downstream throttling problem showing up at the orchestration layer. The hard part is that the delay often appears in one place, while the cause sits somewhere else. A pipeline run may look healthy, the source may respond, and the sink may still reject throughput. Or a Self-Hosted Integration Runtime may be online but too CPU-starved to pick up new