Replies: 1 comment
|
Thank you for your interest in contributing to our community! We currently only accept discussions created through the GitHub UI using our provided discussion templates. Please re-submit your discussion by navigating to the appropriate category and using the template provided. This discussion has been closed because it was not submitted through the expected format. If you believe this was a mistake, please reach out to the maintainers. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Product Feedback
💬 Feature/Topic Area
Self-hosted Runners
Discussion Details
Request: a timeout for the time a job spends queued waiting for a runner.
Today:
timeout-minutesonly starts counting once the job is running. A job that targets an offline self-hosted runner stays queued for up to 24 hours, and nothing downstream can react to it.Proposal: a job-level
queue-timeout-minutes. When it expires, the job ends as failed (or cancelled), so a later job withif: failure()can rerun the work on another runner and the workflow does not hang for a day.All reactions