This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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(121.6, 38%, 21%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECF%3C/text%3E%3C/svg%3E)
Hello,
Since 4 days we have a lot of problems with Data Factory "Copy Data"
As you can see, 5 days ago the "Copy Data" lasted 57 seconds seconds (5 seconds of queue time and 49 of copy)
This morning (and the 3 previous day) the same "Copy data" lasted 9min40 with a Queue time of 9min19 !!!
We are using AutoResolveIntegrationRuntime. The problem is that it causes a lot of timeout .
Can you help us to fix this ?
Thank you
![](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(54.400000000000006, 88%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJW%3C/text%3E%3C/svg%3E)
Also experiencing a very similar issue since the 16th of March. Example from the 16th
Compared to a massive increase since then, including an example from today's DF execution
![](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(172.8, 70%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMM%3C/text%3E%3C/svg%3E)
@Jeremy Watts (Co-op Technology)
Hello and welcome to Microsoft Q&A. Am I to understand both of you experienced a troublesomely large increase in queue times, starting today 2023-03-21 ? In both cases using AutoResolver IR.
There is no user-controlled cause I can think of. The first thing I can think of is a capacity issue on Azure side, or some resource became unhealthy. I'll look to whether there are any known incidents on-going. A 9 minute queue time is egregious. I've experienced a minute queue time on a bad day. Queue > 2 minutes are concerning.
@MartinJaffer-MSFT "Am I to understand both of you experienced a troublesomely large increase in queue times, starting today 2023-03-21" ==> For me, the problem started on 2023-03-17
"In both cases using AutoResolver IR." ==> I use AutoResolve IR
Good news : this morning the queue time is way better than yesterday
@Jeremy Watts (Co-op Technology)
There was an incident today which resulted in the queue times and timeouts. It has since been resolved. You should be able to find more on Service Health in the Azure portal.
Let me know if the symptoms persist.
Hi Martin,
I can confirm that the issue has resolved itself today. I'm hoping it doesn't occur again but this is the 2nd time in March so far that people have raised it as an issue which leads me to believe that MS have yet to fully understand and address the route cause.
Thank you,
Jeremy
I think the two incidents have different root causes. Sometimes they make the root cause analyses are made publicly viewable. We'll see.