Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
This issue is resolved. Thanks!
Some of the CDS connection copy activities in the Azure Data Factory pipelines have been stuck in the queue for a long time.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 6%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDT%3C/text%3E%3C/svg%3E)
Dharma Teja Mukka
0
Reputation points Microsoft Employee
Today, the copy activities using the CDS connection have been stuck in the queue for a long time. Previously, these activities used to complete within minutes, but today they have been in the queue state for 3–4 hours.
Azure Data Factory
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 2%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMK%3C/text%3E%3C/svg%3E)
Manoj Kumar Boyini 16,725 Reputation points Microsoft External Staff Moderator2026-05-29T13:07:09.13+00:00 Thanks for reaching out, I understand you're experiencing unusually long queue times for Azure Data Factory copy activities using a CDS connection. To help diagnose this, I need a few more details:
Which integration runtime type are you using (Azure, Self-hosted, or Managed) and in which region is your Data Factory deployed?
Are all pipelines affected, or only specific ones? When did this issue start occurring?
Are you seeing any error messages or logs in the pipeline run details, or is it only stuck in the queue without errors?
Have there been any recent changes to your Data Factory configuration, CDS connection, or network environment?
Please share the details in Private Message
-
Manoj Kumar Boyini 16,725 Reputation points Microsoft External Staff Moderator
2026-06-02T12:36:01.7133333+00:00 Just checking in to see if the information provided earlier was helpful. Please let us know if you need any additional details or assistance, and we’ll gladly continue supporting you.
Sign in to comment
4 answers
Sort by: Most helpful
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(118.4, 78%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDT%3C/text%3E%3C/svg%3E)
Dharma Teja Mukka (HCL AMERICA INC) 0 Reputation points Microsoft External Staff2026-06-04T05:52:37.65+00:00 -
Manoj Kumar Boyini 16,725 Reputation points Microsoft External Staff Moderator
2026-06-01T16:52:02.28+00:00 This behavior was due to a transient issue in the region, which caused some ADF copy activities (especially CDS connections) to remain in the queued state for longer than expected. The issue has since been mitigated, and pipeline executions should now be proceeding normally.
As part of ongoing improvements, the engineering team is continuously enhancing detection and recovery mechanisms to better identify and resolve such situations proactively.
We sincerely apologize for the inconvenience caused. If you notice similar behavior again, please reach out and we will prioritize engagement with the Product team.
-
kagiyama yutaka 3,605 Reputation points2026-05-29T13:47:53.69+00:00 I think a short test‑copy and an Azure Service Health check are the user steps when a CDS copy stays Queued, and sending the run IDs to Azure support is the next step.
-
Dharma Teja Mukka 0 Reputation points Microsoft Employee
2026-05-29T13:13:45.75+00:00 Hi Manoj, Thanks for the response.
ADF region: West US 2
We are currently using Integration Runtime without Managed Virtual Network. Recently we changed Integration Runtime for all the pipelines. Previously IR was with Managed Virtual Network now we changed it to without Managed Virtual Network.IR region is Auto Resolve. We updated 10 days back. Only today we are facing this issue.
Only few pipelines we are facing this issue.