{"version":"2.1.295","anchor":"self-hosted-runner-forced-refresh-and-in-private-checkoutt","canonical_anchor":"self-hosted-runner-forced-refresh-and-in-private-checkoutt","heading":"Self-hosted runners can force an immediate refresh","tier":"notice","area":"Self-Hosted Runners","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/self-hosted-runner-forced-refresh-and-in-private-checkoutt","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Self-hosted runners can force an immediate refresh\n\nSelf-hosted runners can now force a refresh that skips the usual wait and re-runs right after one already in progress\n\n**What**\n\nA self-hosted runner is a machine you run yourself that starts Claude Code sessions. Its refresh step can now be forced. Before, a refresh request was simply turned away if one was already running or one had run too recently. Now:\n\n- A forced refresh skips the short waiting period between refreshes.\n\n- A forced refresh asked for while another is running runs again as soon as that one finishes.\n\n- A failed forced refresh retries straight away.\n\nThe runner also now tells a session whether it is running in a private checkout of the code, reports whether a failed run was running as a thread, and removes one more home-directory path when cleaning up paths for its git proxy.\n\n**Why**\n\nThese changes make self-hosted runners more robust.\n\n- Area: Self-Hosted Runners\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}