Understanding execution order of Jobs/Workflows #121202
Replies: 1 comment
-
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Beta Was this translation helpful? Give feedback.
-
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