{"version":"2.1.317","anchor":"worker-registration-failures-report-http-status","canonical_anchor":"worker-registration-failures-report-http-status","heading":"Remote worker setup failures now record the HTTP status","tier":"internal","area":"Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/worker-registration-failures-report-http-status","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Remote worker setup failures now record the HTTP status\n\nWhen a remote session worker fails to register, Claude Code now records the HTTP status and whether the server answered at all\n\n**What**\n\nIn remote sessions, Claude Code first registers a worker with the remote service. When that registration fails, the connection closes with an error code. That close step used to receive no details. It now receives:\n\n- the HTTP status the server answered with, a number such as 500 that says what went wrong\n\n- whether the server gave no answer at all\n\n**Why**\n\nThis makes it easier to diagnose why a connection to a remote session could not be set up.\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}