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(227.2, 59%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGD%3C/text%3E%3C/svg%3E)
We are looking for guidance surrounding the 2 day limit on Managed DevOps Pools. Currently we have pipelines that are expected to go beyond the 2 day limit (up to 30 days). This is common for us due to the nature of what we do.
According the website:
"Can run long-running workflows up to two days long. Contact support if your workflow requires you to run a single job that takes more than two days to complete"
We want to understand what this process is.
We also want to check if it is possible to cover an entire pool with the ability to run longer than two days.
Answer accepted by question author
![](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(73.60000000000001, 77%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERM%3C/text%3E%3C/svg%3E)
Hi @Garrett Dribusch ,
Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.
We have a received a response from the backend team, they said:
The published docs were incorrect and have been updated. You'll need to split your job into smaller pieces of work that can run under 2 days. This is a hard limit in Azure DevOps by design and not on our pools.
Unfortunately, you'll have to run these jobs in smaller pieces under 2 days.