-
Type:
Suggestion
-
Resolution: Unresolved
-
Component/s: Pipelines - Deployments
-
None
-
1
Currently, if a step is queued for more than 4 hours in a concurrency group, it'll be timed out and goes to halted state.
In some scenarios, say multiple PR builds are triggered, and each build takes ~ 2 hours, by the time it gets to the queued steps, some of them will be halted due to the 4 hours timeout.
It would be beneficial to have a capability to increase the timeout.