{"version":"2.1.311","anchor":"self-hosted-runner-refuses-code-review-sessions-when-the-ser","canonical_anchor":"self-hosted-runner-refuses-code-review-sessions-when-the-ser","heading":"Self-hosted code review sessions refuse to start if the service's hooks are rejected","tier":"notice","area":"Self-Hosted Runners","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/self-hosted-runner-refuses-code-review-sessions-when-the-ser","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Self-hosted code review sessions refuse to start if the service's hooks are rejected\n\nA self-hosted code review session will not start when the launcher hooks sent by the service fail checks or cannot be registered\n\n**What**\n\nSelf-hosted code review sessions have another reason to refuse to start. The service sends launcher hooks with each review, which are steps to run around the session. The runner now will not start the review when:\n\n- the hooks fail its checks, with the message that the service sent launcher hooks that this runner cannot accept\n\n- the hooks could not be registered\n\nIt explains that a code review is not started without the hooks that the service sent for it.\n\n**Why**\n\nIf you run self-hosted review sessions, this is a new refusal you may see, and the message tells you the hooks were the cause.\n\n- Area: Self-Hosted Runners\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: yes"}