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(224.00000000000003, 77%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERA%3C/text%3E%3C/svg%3E)
A pipeline that ran yesterday, hasn't been changed since is now failing with "Triggering the pipeline failed due to large run size"... is there a limit to the number of pipelines/size of other running pipelines that can cause this? I do have another process running that is looping a large number of files, is that likely to be a cause? If so, what can be done to allow another pipeline to run at the same time?
If not, why is Data Factory so unstable that a pipeline sometimes has an issue with "Triggering the pipeline failed due to large run size"?
Hi @Ryan Abbey ,
Thank you for posting query on Microsoft Q&A Platform.
This might be because of your ADF may crossed some limitations. Below image shows few. Click here to see full list of ADF limitations.
Please let us know if that helps or any further queries. Thank you.
Thanks for the detail but highly doubtful we've got that high... at most we had 1 pipeline running (the failed to start one would have made it 2 concurrent pipelines). The pipeline that was running was running sequential so should never have been more than a few concurrent activities
Hi @Ryan Abbey ,
If that is not the case and still you are facing issue then I would encourage you to have a support ticket for this to deeper investigation. Thank you.