{"version":"2.1.274","anchor":"force-login-org-policy-validation-failures-now-get-logged","canonical_anchor":"force-login-org-policy-validation-failures-now-get-logged","heading":"Force-login-org \/ policy validation failures now get logged and reported with a reason","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/force-login-org-policy-validation-failures-now-get-logged","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Force-login-org \/ policy validation failures now get logged and reported with a reason\n\nFailed org\/policy validation during headless startup now gets logged with a reason\n\n**What**\n\nWhen Claude Code runs in headless mode (`--print`) and account or organization policy validation fails, it now records a report before erroring out. If the policy couldn't be read (`policyUnreadable`), a `policy_invalid` event is reported. In the final force-login-org check, a failure now also logs the session ID, message, and reason, and runs an additional cleanup step.\n\n**Why**\n\nThis gives better visibility into why a headless session was blocked by organization policy, making these failures easier to diagnose instead of just failing silently.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}