{"version":"2.1.296","anchor":"self-hosted-runner-register-errors-now-explain-work-order-an","canonical_anchor":"self-hosted-runner-register-errors-now-explain-work-order-an","heading":"Self-hosted runners explain why they could not register","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-register-errors-now-explain-work-order-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Self-hosted runners explain why they could not register\n\nSelf-hosted runners now say when a work order is used up or when the organization has not allowed self-hosted environments\n\n**What**\n\nA self-hosted runner is a machine you run yourself that does Claude Code work for your organization. When it starts, it registers with Anthropic's servers. Registration failures used to give a generic message, and a refusal said the token might be revoked. They are now sorted into specific cases:\n\n- A work order that was refused, expired, or reported as not redeemable or no longer active. The message says a work order is single-use and short-lived, that restarting the runner with the same one cannot help, and that you should not rotate the environment secret.\n\n- An organization that has not allowed self-hosted environments. The message points to the 'Allow self-hosted environments' admin setting.\n\nOther server errors now include the error type, the reason and the server's own message.\n\n**Why**\n\nPeople running self-hosted runners get a message that says what to fix. They are no longer pointed at rotating secrets when the real cause is a used-up work order or an organization setting.\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"}