You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can someone help me to understand in which order Jobs/Workflows are executed? We are currently ARC in our AKS running something like up to 150 runners. Filtering actions for queued state I can see Workflows queued up to 40 minutes ago and not started yet. That would not be an issue in itself. Strang is though, that I see new Workflows being queued and immediately picked up as soon as one runner is free. Feels like first in last out? I do not find any documentation on the expected behaviour. But this feels counter intuitive. Who controls the order? Github? Or is it maybe ARC which is introducing an issue here?
ActionsBuild, test, and automate your deployment pipeline with world-class CI/CDQuestion
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Select Topic Area
Question
Body
Can someone help me to understand in which order Jobs/Workflows are executed? We are currently ARC in our AKS running something like up to 150 runners. Filtering actions for queued state I can see Workflows queued up to 40 minutes ago and not started yet. That would not be an issue in itself. Strang is though, that I see new Workflows being queued and immediately picked up as soon as one runner is free. Feels like first in last out? I do not find any documentation on the expected behaviour. But this feels counter intuitive. Who controls the order? Github? Or is it maybe ARC which is introducing an issue here?
Beta Was this translation helpful? Give feedback.
All reactions