{"version":"2.1.296","anchor":"self-hosted-runner-troubleshooting-doc-adds-work-order-and-o","canonical_anchor":"self-hosted-runner-troubleshooting-doc-adds-work-order-and-o","heading":"Self-hosted runner troubleshooting covers three more failures","tier":"notice","area":"Self-Hosted Runner","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/self-hosted-runner-troubleshooting-doc-adds-work-order-and-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Self-hosted runner troubleshooting covers three more failures\n\nThe built-in troubleshooting table for self-hosted runners now covers unenabled organizations, single-use work orders and on-demand poll auth failures\n\n**What**\n\nA self-hosted runner is a machine you operate yourself to run Claude Code cloud sessions. The troubleshooting table that ships with Claude Code for these runners has three new rows:\n\n- the error \"RegisterRunner refused because self-hosted environments are not enabled for this organization\"\n\n- a refusal because a work order can only be used once\n\n- an authentication failure while an on-demand runner checks for work\n\n**Why**\n\nOn-demand runners take their jobs from work orders, and these rows describe how that works when it goes wrong.\n\n- Area: Self-Hosted Runner\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}