{"version":"2.1.314","anchor":"dispatch-403-distinguishes-revoked-dispatch-token","canonical_anchor":"dispatch-403-distinguishes-revoked-dispatch-token","heading":"Self-hosted environment errors now flag a revoked dispatch token","tier":"notice","area":"Self-Hosted Runners","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314\/e\/dispatch-403-distinguishes-revoked-dispatch-token","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.314","markdown":"### Self-hosted environment errors now flag a revoked dispatch token\n\nA refused request from a self-hosted environment runner now records when the cause was a revoked dispatch token\n\n**What**\n\nWhen a self-hosted environment runner gets an access-denied (403) error, Claude Code now checks whether the cause was a revoked dispatch token. If so, the error records that, with a more specific reason. Before, the only case it singled out was self-hosting being turned off by your organisation.\n\n**Why**\n\nThis makes it easier to see why a self-hosted environment could not authenticate.\n\n- Area: Self-Hosted Runners\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}