Skip to main content

Recover runners whose removal is stuck

Removing a node's GitHub runners waits for each runner to finish its current job, then the node removes it and deletes its files. The pool stays on the node's page until the node reports that none are left. If the node has gone, or can't finish the job, the pool stays there. Use this page to bring it back, try again, or let go of it and remove the runners in GitHub yourself.

Who can do this: requires the org admin role, and your plan must include GitHub runners. Put the pool back also needs the permission to edit nodes; Ask the node again and Drop the record need the permission to delete nodes.

Recover the pool​

  1. In the sidebar, select Directory, then the Machines tab.
  2. Select the node's name, then its GitHub Runners tab.
  3. Read the pool's line. Removing means the node is still working through the runners; hover it to see how many are still active. Removal failing means the node's last attempt failed, and a red banner above gives the node's own error. The node tries again on its next pass either way, so a long job alone is no reason to act.
  4. If you want to keep the runners after all, select ↩ (Put the pool back). The pool goes back to running with the same repository, credential and number of runners.
  5. If the node is back online or the error is fixed, select ↻ (Ask the node again). It sends the same removal again, without asking you to confirm.
  6. If the node is gone for good, or nothing can read its runners, select ⊘ (Drop the record — runners stay registered in GitHub). The dialog Drop the runner pool record for and the node's name says how many runners the node last reported.
  7. Select Drop the record. The tab says Record dropped. Runners still registered in GitHub keep taking jobs until removed there.
  8. Remove the leftover runners in GitHub: open the repository's Settings, then Actions, then Runners, and remove each one. If the machine still exists, delete the runners' files on it too.

Dropping the record removes nothing from GitHub or from the machine, and Jaah no longer holds the credential that could remove them from GitHub. Until you remove them in GitHub, those runners can still take jobs.

To set up a pool again, or for how removal normally works, see Run GitHub runners on a node. If you are retiring the machine, see Delete a node.